These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
Integrations
Connect support intake and feedback without losing event identity.
- Incoming requests
- Support intake channelsin and out
- Replies and surveys
- Message and survey providersout
- Customer and knowledge context
- Identity and knowledge sourcesin and out
- Reporting exports
- Authorized analytical consumersout
- Agents
- Your agentWorks within the permissions you assign
Incoming requests
- Support intake channels. Connect the support mailbox, portal or web form and authorized system webhooks. Resolve customer identity separately from an email match, and retain one ticket per accepted source event. Manual phone intake records an agent-entered request.
Replies and surveys
- Message and survey providers. Send public replies and post-closure invitations through the configured provider. Keep accepted, failed and unknown outcomes distinct. A timed-out response may still have been accepted externally, so reconcile the original message identity before retrying.
Customer and knowledge context
- Identity and knowledge sources. An HR or CRM source can supply identity references for reviewed mapping. It cannot grant portal permission by importing an email address. Knowledge links point to an approved source under that source’s own access rules.
Reporting exports
- Authorized analytical consumers. Export only authorized ticket and episode fields. Internal content remains private, and a notification or analytics connector cannot broaden a customer’s access.
How connections are governed
service accounts, audit, pausingAuthenticate each intake event and provider callback, bind it to the configured workspace and preserve its original request identity. Store credential references outside source documents. Deduplicate intake, replies, assignments, escalation, breach and survey commands. Reconcile unknown email or survey outcomes before a fresh send. A connection acknowledgment is delivery evidence, not customer resolution or a CSAT response.
The API is one more client of the same interface. Agent and automation →
# Example work after configuration
$ curl -s erp.ai/skill.md
› Prepare a draft response policy using our business calendar for manager review.
› Show my assigned tickets with an unanswered customer question and a near-term service target.
› Summarize this permitted ticket for the named L2 recipient, keeping internal notes private.
› Reconcile this survey delivery using its existing request identity.