Skip to content
Chat on your store is live, answered from the same inbox.
GROWTH DEPT.HELPDESK

Integrations

Connect the tools your store runs on.

Your store, your mail, your own code. Every tile says whether it works today, so you know what you are getting before you book.

Where most stores start

Everything else

Send ticket changes to your own systems

Add an HTTP integration with a URL, a method and a body template, and pick the events it sends on: a ticket created, a ticket updated, a message added. Fields in double braces are filled in from the ticket for each delivery.

Use it to tell a warehouse app about a damaged-item ticket, keep your own copy of ticket status, or post each new ticket to a Slack channel through an incoming webhook.

URL

https://hooks.example.com/helpdesk

Method

POST

Content type

application/json

Send on

  • Ticket created
  • Ticket updated
  • Message added

Body

{"ticket_id": {{ticket.id}},
 "status": "{{ticket.status}}"}

One request per event, signed

Each event becomes one request built from your template. Deliveries are signed, and retried with a growing delay when your server does not answer.

POST https://hooks.example.com/helpdesk
Content-Type: application/json

{
  "event": "ticket-created",
  "ticket_id": {{ticket.id}},
  "subject": "{{ticket.subject}}",
  "status": "{{ticket.status}}"
}

For brands Growth Dept runs

The Growth Dept kit's support tools (the ticket mirror, reply drafts, triage, automation and the support dashboard) move to this helpdesk with one setting on the brand's machine.

The switch checks that the helpdesk answers with the brand's key before it changes anything.

# On the brand's machine: check first, change nothing
bin/switch-backend --to growthdept

# Then switch the kit's support tools to this helpdesk
bin/switch-backend --to growthdept --execute

Missing something you rely on?

Book a call and tell us what you connect to today. We say plainly what works now and what does not.