Michael O'Brien ยท

Your engineers are answering support tickets

What to set up before your first enterprise customer emails a founder at 7am.

The first enterprise pilot goes live, and a week later the customer's admin emails a founder at 7am because single sign-on broke for half their team. The founder forwards it to an engineer, who fixes it, replies, and loses the morning. That works for the first customer. By the fifth, your engineers are running support, which wasn't in the plan you showed the board.

I've built support operations from both ends. At Uber, investigations started as part of one role and grew into a 130-person program across two sites. At Boston Dynamics, I led the rebuild of support.bostondynamics.com, where the products are robots with hardware revisions. The first steps were the same both times.

Decide who a customer contacts

Give customers one address or one form, and write it into the pilot agreement. When the product is down, the customer shouldn't have to guess which founder to text. Behind that address, one person owns the first reply each day, even if the job rotates through the engineers.

Write down what urgent means

An outage for a customer's whole team and a typo on the dashboard are different problems. Agree on a few levels, what each one means for the customer, and how fast each gets a reply. Put it in the pilot agreement too, so the customer knows what to expect before the first ticket. At Uber, one rule in the escalation redesign was that an urgent issue that confused triage bypassed tier 1 and went straight up. Better analytics and that redesigned escalation process cut time-to-solve on critical security escalations by half. At five customers the same rule works: if the person reading the ticket can't tell what it is, it goes to the engineer who can.

Keep the answers where the next person can find them

Every fixed issue is an answer someone will need again, usually at a worse hour. The support.bostondynamics.com rebuild integrated Salesforce, Jira, and Paligo so cases, engineering tickets, and published articles lived in connected systems. At five customers, a shared doc and a tag on each ticket do the same job. Start the habit while the volume is small.

Count the tickets

A weekly count by customer and by type shows which part of the product is costing engineering time, and when support needs a person of its own. Without the count, the hire tends to happen after the engineers are already behind on the roadmap.

Next step

Who answered the last support email?

The last ten tickets will show how much of an engineer's week support already takes, and who should answer the next ten.