Connect Trengo
The inbox Maximal reads tickets from and writes drafts into. About an hour, most of it in Trengo.
What you will need
- A Trengo workspace, and an account on it that can create API tokens.
- An API token, created in Trengo under Settings, Apps and integrations.
Connect it
Create the token in Trengo
Give it a name you will recognise in six months, Maximal for instance, so revoking the right one later is obvious.
Paste it into the Connect screen
/screens/onboarding. The token is encrypted at rest, scoped to your account and never written to a log.
Let it register the webhook
Maximal registers its own webhook and stores the signing secret Trengo returns. Every inbound message is verified against that secret before anything reads it, so a forged request cannot start a run.
What it does in your inbox
| It does | It does not |
|---|---|
| Read incoming messages on connected channels | Send anything to a customer |
| Look up the order the message is about | Close, merge or reassign a ticket |
| From stage 1: attach a drafted reply as an internal note | Change your team’s settings, labels or rules |
A draft is an internal note: your team sees it, your customer does not. During a shadow week, at stage 0, not even that is posted. Nothing leaves the inbox without a person sending it.