Dixa
Dixa is a customer support platform Pinch merchants use as the outbound channel for customer communication. The Dixa integration is what lets Pinch send transactional emails to customers from your own domain when a Playbook fires.
What the connection is used for
Pinch uses the Dixa connection for one thing: sending customer emails on your behalf when a Playbook's segment is entered. Pinch does not read tickets, conversations, or agent activity from Dixa.
Typical emails Pinch sends via Dixa:
| Customer segment | Example email |
|---|---|
| VIP | "Thanks for being a great customer — your next return is on us. Use this link for an instant exchange." |
| Suspect | "We noticed a higher return rate on your account recently. Here's how our return policy works going forward." |
| Egregious | "Your account has been removed from our standard return program. If you have questions, reply to this email." |
| Pinch-First-Order | Welcome / first-order onboarding email. |
| Pinch-Second-Order | Repeat-buyer thank-you with cross-sell. |
| Returns blocklist | Policy-change notification when a customer is moved to the deny list. |
| Any custom segment | Anything you want to send to a Customer List or workflow-generated segment. |
The Dixa connection is segment-agnostic. Pinch can send to any segment — VIP, Suspicious, Egregious, custom workflow-generated segments, or customer lists you've built on the Customers page.
How emails are composed
Email bodies come from Email Templates you author in the Pinch dashboard. Variables like {customer_name}, {order_number}, and {RETURN_POLICY_LINK} get interpolated at send time. Pinch hands the rendered email to Dixa, which delivers it from your configured sender domain and writes the outbound message into the customer's Dixa conversation history so your agents see it.
How to connect
In the Pinch dashboard, go to Integrations → Customer Support → Dixa. Authenticate with a Dixa API key from your Dixa admin (Dixa → Settings → API). The connection takes effect immediately; Playbook Email actions targeting Dixa start working on the next segment entry.
What this is NOT
- Pinch does not read your Dixa tickets, conversations, or agent activity.
- Pinch does not surface risk data inside Dixa's agent UI (that's a separate roadmap item).
- The Dixa connection is purely an outbound email channel for Playbook actions.
See also
- Playbooks — where Email actions are configured
- Email Templates — the reusable bodies Pinch sends via Dixa
- Gorgias — the same capability via Gorgias if you're on that stack