Zendesk + Outcome
Zendesk hears your customers in the greatest volume. Outcome decides which goal each complaint bears on. Together, tickets become themes counted by the organisations that raised them, and CSAT and reply times measure whether the fix worked.
Zendesk brings the facts. Outcome turns them into decisions.
| Use | From Zendesk | What Outcome does with it |
|---|---|---|
| Structure |
| Each goal gets an owner, and each piece of work a team. |
| Measures |
| A goal's number is read on a schedule, with its history. |
| Signals |
| Grouped into themes and put in front of the goal they bear on. |
Zendesk + Salesforce + Atlassian + PostHog + Outcome
What it never reads
- Requesters, agents and anyone copied
- Internal notes, later replies and attachments
- Satisfaction comments
- Writes of any kind to Zendesk
Status
Preview Customer feedback
Live In the product today. Preview Working, refined with customers.
Connected in minutes, by an admin.
- 01Open
An owner or admin opens Settings, Integrations, Zendesk.
- 02Connect
Paste: Admin email, API token.
- 03Read
Outcome reads it on the schedule you set, from the first day.
- 04Done
Nothing is ever written to Zendesk.