Client Touchpoints When the Client Won't Take a Meeting

Find Out What the Client Is Declining

Ask: Is the issue the meeting time, the agenda, or how you'd rather receive the information? Then use the answer to change the contact method. You need to understand the obstacle before sending another version of the same invitation.

If the client says there is nothing to discuss, reply: The update can stay in writing. The decision I still need is [decision], because [business consequence]. That makes the request specific without pretending a full review is required for every answer.

Don't assume a declined meeting means the relationship is failing. Check the actual account work and the client's stated reason. A contact preference and an unresolved service problem need different responses.

The model calls for reviewing client margin and fit each quarter. Keep that internal review even when the client prefers lighter contact. A meeting cancellation doesn't remove the account owner's work of checking whether the service arrangement still fits.

Choose the Lightest Contact That Can Finish the Job

Use the options below as a proposed progression when the current format doesn't get the required result. You don't need to make every client climb through every format. Move because the decision needs something more, rather than because your sequence has another message scheduled.

Keep the underlying account record consistent across those formats. The client shouldn't receive an email saying a decision is open while the project record says it was approved. Have the contact owner update the accepted result where the delivery team can find it.

Give a report a purpose beyond showing that the tools ran. Point to the finding that matters and explain the choice it creates. Sending a large attachment doesn't establish that the client has understood or authorized the next action.

Write the Decision Note So Someone Can Answer It

Use this opening: [Client name], here's the result that needs your attention. [Plain finding] affects [business work]. Please confirm [specific decision] so we can [authorized next action]. Fill it from the actual finding rather than borrowing a generic security warning.

Put the relevant evidence where the contact can reach it through the agreed route. Explain an unresolved assumption plainly. If the client needs a technical colleague to interpret the finding, arrange that help before demanding a choice.

What if the client replies that they don't have time? Say: I can keep the update in writing. To finish [specific work], we still need [decision]; who should make that choice? That gives the contact a way to route the work rather than simply decline the calendar request.

Keep a genuine decision date tied to the reason it exists. If a supplier notice deadline or an agreed project dependency creates the date, record that basis. Don't manufacture urgency to make the client take a meeting.

Reduce Repeated Questions With Agreed Standing Choices

On Paul Green's podcast, a guest presented as Jason describes new-starter delays from repeated license questions and sign-off. He would prefer an agreed record of the usual choices. The host notes that another client might want to approve every addition.

Use that account as a prompt to ask what this client wants. Say: These requests keep needing the same decision. Would you like to agree the standard choice and approval limits, or keep approving each request? Record the authorized answer before changing the route.

A saved preference isn't permission for every variation. Keep exceptions with the person who can approve them. The team still needs to know when a request falls outside the standing choice.

Review those choices when the client's work changes. The aim is a usable decision record, rather than fewer conversations at any cost. A quick process that carries the wrong permission still needs correcting.

Escalate the Decision Without Making It a Personal Dispute

If an important decision remains unanswered, tell the contact what is waiting and what can't proceed. Use the escalation route agreed for the account. Keep the message about the work rather than describing the client as difficult.

Say: We haven't received approval for [work]. [Named task] is waiting, and [stated consequence] remains. I'll raise this with [appropriate contact] through our agreed route so we can establish the next step.

Erick Simpson recommends bringing leadership into potentially difficult client conversations while the technician stays focused on helping the user. That's his practitioner relationship-management suggestion. Keep the commercial or account decision with someone who can settle it rather than making the service technician argue for a review meeting.

Use a focused meeting when the people involved need to resolve competing priorities together. Send the decision and relevant evidence in advance. Give the invitation an outcome the client can recognize, then record the actual result afterward.

Measure the Decisions Alongside the Contact

Record the method and result of each meaningful contact in the CRM or account record. Count decisions still unanswered against their actual required dates. Review the cases instead of treating a sent email or a completed meeting as proof the account is healthy.

Generic sales advice to keep in touch leaves an MSP's service decisions unfinished. The contact has to connect the client's choice with approved delivery work. A friendly update alone doesn't establish whether a purchase or change is authorized.

Look for repeated confusion in the replies. If the client asks what you want them to decide, fix the question. If the contact lacks authority, fix the route rather than increasing the number of reminders.

Start with an actual account decision waiting behind a declined meeting. Send the shorter note with the evidence and the person authorized to answer. Move to a conversation when the reply or the unresolved consequence shows why it is needed.