Skip to content

Guides

Handle a customer who wants to talk to the founder

Some customers ask for the founder because they think it is the fastest route. Sometimes it is, and sometimes it hides a problem you can fix without them.

Last reviewed

Find out what they actually want

Ask what they hope the founder can do. Most want a decision, an apology or proof someone senior cares, and you can often supply that yourself.

Decide when the founder really should step in

Loop them in for a large account at risk, a public complaint or a legal threat. Skip it for a routine bug or a refund your policy already covers.

Reply without sounding like a gatekeeper

Say you have read the message, say what you will do and by when, and offer to pass the details along. Never promise a founder reply you have not agreed.

Brief the founder properly

Send a short summary: who the customer is, what happened, what they asked for and what you recommend. The founder should never have to read the thread.

Close the loop and learn from it

Record the outcome on the ticket. If the same request keeps arriving, fix the cause, such as a missing escalation path or an unclear policy.

Questions

When should a founder join a support conversation?

When a large account is at risk, a complaint is public or the decision is above support policy. Routine issues stay with support.

What if the customer insists on the founder?

Be honest about what you can resolve, offer a clear timeline and pass the case on if it meets your escalation rule.

How do we stop founders being pulled in all the time?

Write down the cases that qualify, give agents the authority to settle the rest and review the exceptions monthly.

Written by Flatdesk, a help desk for small support teams at one flat price per agent. Try it free for 14 days, no card.