Integrations
Connect customer identity, event triggers and delivery with explicit ownership.
- CRM identity and ownership
- ConnectionCustomers, Employees · in
- Helpdesk and customer events
- Connectionin and out
- Email, SMS and in-app delivery
- Connectionin and out
- Benchmark and classification providers
- ConnectionComments · in and out
- Agents
- Your agentWorks within the permissions you assign
CRM identity and ownership
- Connection. Import Customers and Employees through trusted mappings before sending or assigning outreach. CRM owns canonical customer data. Missing, stale or cross-tenant references remain exceptions; app staff cannot edit a mirror to make a campaign eligible.
Helpdesk and customer events
- Connection. Authenticate the source system and stable event ID for a completed ticket, onboarding, purchase or renewal. Resolve one eligible occurrence. A repeated event returns its original invitation, while a later eligible interaction retains its own occurrence identity.
StatusQueuedSendingSentUnknownFailedSuppressed
Email, SMS and in-app delivery
- Connection. Use the configured provider with stable request keys and verified callback correlation. Track accepted, failed and uncertain attempts separately. Current suppression applies at each dispatch and reminder. Provider callbacks never declare a completed survey response.
StatusQueuedSendingSentUnknownFailedSuppressed
Benchmark and classification providers
- Connection. Pin the benchmark metric, scale, population and period. Incompatible comparisons remain unavailable. Configure the permitted processor and data policy before classifying comments; do not assume automated masking removes every identifier.
How connections are governed
service accounts, audit, pausingKeep connectors disabled until source identity, tenant scope, consent, callback authentication and idempotency are tested. CRM and Helpdesk remain their record owners. A provider timeout stays Unknown until the original request is reconciled. Private correlation, raw tokens and secrets are not staff report fields.
The API is one more client of the same interface. Agent reference →
# Example work after configuration
$ curl -s erp.ai/skill.md
› Prepare a support CSAT campaign that waits one hour after resolution and respects current opt-outs.
› Explain this NPS change using the original instrument and comparable cohort population.
› Show my attributable detractor follow-ups that still need a recorded outcome.