Connect your store, CRM, chat and help desk
Agents read from every connected source, so answers come from your real data and not a guess. Every integration is one click OAuth.
Support Agent answered a shipping question using your Shopify order record and the care guide, and showed both sources.
An agent is only as good as what it is allowed to read.
An assistant that cannot see your order records will guess about shipping. One that cannot see your help desk will answer a question your team already answered better last week. Most disappointing AI deployments are not a model problem, they are a context problem.
So the integrations are not a checklist feature here, they are the thing that decides whether the agents are useful. Connect the systems where your truth already lives and the answers stop being generic.
At a glance
- Integrations available
- 25 and growing
- Setup
- One click OAuth
- Default access
- Read only
- Sync frequency
- Near real time via webhooks
- Anything else
- Zapier, or the REST API
- Availability
- Core set on Growth, all on Premium
Everything included
Everything below works out of the box, with no custom development required.
One click OAuth, read only by default
No API keys pasted into a settings box, no engineering ticket. Authorise from the dashboard and the connection is live. Agents can only read until you explicitly grant write access, per integration.
Commerce and payments
Shopify, WooCommerce, BigCommerce, Squarespace and Wix for orders and products. Stripe, PayPal, Razorpay, Adyen and Apple Pay for memberships and tickets. Order status becomes something an agent can answer accurately.
Chat where your people already are
Slack, Discord, WhatsApp, Telegram and Discourse. Mirror announcements outward, or pull questions in so they get answered once and stay searchable rather than scrolling away.
Support and CRM, both directions
HubSpot, Salesforce, Intercom, Zendesk and Freshdesk. Anything an agent cannot answer becomes a ticket with the full conversation attached, and member records stay in sync with your CRM.
Marketing and analytics
Mailchimp, Klaviyo, Google Analytics, Zapier and Segment. Community activity lands in the same funnel as everything else, and Zapier covers anything not on the list.
Sources are visible in every answer
When an agent answers, it shows which connected source it used. If a source goes stale or a connection breaks, you see it in the dashboard rather than discovering it through a wrong answer.
Loyalty and points platforms
Smile.io, LoyaltyLion, Yotpo and Shopify native points sync both directions. Members see one balance whether they are in your store or the community, and it is always the same number.
Webhooks and a REST API for the rest
Subscribe to any community event, or read and write through the API. Rate limits are generous and the OpenAPI spec is published, so anything not on the connector list is still an afternoon of work.
Points that follow the member
A loyalty balance that only exists in your checkout is invisible for the 29 days a month a customer is not buying anything. Syncing it into the community puts the number in front of them while they are reading, asking and posting, which is when it can actually change what they do next.
- Two way sync with Smile.io, LoyaltyLion, Yotpo and Shopify points, so balances never disagree.
- No programme today? We can run one inside the community and you set the earn rules.
- Award points for community behaviour as well as orders, such as answering a question or posting a review.
- Redeem for store discounts, event tickets, early access or a members only group.
- The Insights Agent reports which earn rules actually move repeat purchase, so you can drop the ones that do not.
Your balance
4,280
points, synced from your store
Synced with Shopify, two way
How it goes live
- 1
Authorise the sources you trust
Pick from the directory and authorise. Most teams start with their store or help desk, since that covers the majority of repeat questions.
- 2
Choose what each agent may read
Scoped per agent, so the Support Agent can read your docs and orders while the Engagement Agent only sees community activity.
- 3
Watch the first answers
Keep the Support Agent on approve mode for a few days and read what it drafts. This is the fastest way to find the gaps in your own documentation.
- 4
Move to auto and add sources
Once the answers are right, let it run. Add sources over time, and the answers get more specific with each one.
Included with this solution
- Commerce: Shopify, WooCommerce, BigCommerce
- Payments: Stripe, PayPal, Razorpay
- Chat: Slack, Discord, WhatsApp, Discourse
- Support and CRM: HubSpot, Salesforce, Intercom, Zendesk
Integrations specifics
Can agents write to our systems?
Only if you turn it on, per integration. The default is read only everywhere. Write access is most commonly enabled for creating a help desk ticket, which is low risk and saves your team retyping context.
What if the tool we use is not listed?
Zapier covers several thousand apps, and there is a REST API with webhooks for anything custom. If a source matters to a lot of customers we will usually build a first party connector for it.
How do you keep our data safe?
Tokens are encrypted at rest, scopes are the minimum each integration needs, and you can revoke any connection instantly from the dashboard. We do not train shared models on your community content or your connected data.
Ways to run the same platform
- Whitelabelled Website
Your own branded community, live in days
Your domain, your logo, your colours. Our name appears nowhere.
- In App SDK
Drop a community module into your product
Feed, groups and support threads inside your app, using your own auth.
- Custom App
An app shaped around how your brand works
Your own app on both stores, with the community and agents inside it.
See integrations with your own brand on it
Book a demo and we will set it up with your data before the call.
Thirty minutes. No credit card, no obligation.