Hugs, built into your product.
Your customers’ agents need people to say yes. Don’t build approvals, inboxes and audit trails yourself — give each customer a getHugs org from your product, and let their agents ask.
Human gates, without building them.
An org per customer
Your product creates a getHugs org for each of your customers — its first workspace, and its owner invited by email — and sets up its people, channels and sources.
Your ids, not ours
Every org, person, workspace and channel can carry your own reference. Creating it again with the same reference returns the same record, so provisioning can run twice.
Only your customers
Your tokens reach your orgs and nothing else. Rotate them freely, keep production and staging apart, and give each only the scopes it needs.
Answers back in your product
Your customers’ people answer in getHugs — by email or in their inbox. Webhooks bring each Hug back into your product as it happens.
Three steps, then it runs itself.
- 1
Provision
When a customer turns the feature on, your product creates their getHugs org with your partner token.
- 2
Hand out keys
Create a source for each of their agents and pass its key along — your product never asks people itself.
- 3
Their agents ask
At every step that needs a person, the agent opens a Hug. Their people answer; the agent carries on.
What’s there today
- The site API for orgs, people, workspaces, channels, sources and templates
- Partner tokens with scopes, limited to your orgs
- External references on everything you provision
- Usage numbers for your orgs
- Webhooks from each customer’s channels
- Hosted at gethugs.ai
Let’s hug it out.
Tell us about your product and your customers’ agents — we’ll set you up as a partner.
[email protected]