Spaces

Confirmation messages for telecom set-up, ports and engineer visits

These confirmation messages let a small telecom firm repeat back what a customer asked for, such as a new line, an engineer visit, a number change or a callback. They give the date and the next step so nothing is left to guess.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

In telecom a misunderstanding is costly. A number moved on the wrong day, an engineer sent to the wrong floor or a service switched on without the customer knowing can all cut a business off or add a surprise to a bill. A short confirmation catches the mistake while it is still easy to fix.

Fill in the date and the detail, choose the message that matches the request, and send it as soon as a person has agreed to it. Your agent can send the same wording once a team member confirms. It should never confirm a port or a bill change by itself.

Engineer visit

Thank you for booking with [business]. Our engineer will visit [when] for the following: [detail]. Please make sure someone can give access, and reply here if the time stops suiting you.

Service change

This is [business] confirming what we agreed: [detail]. It will take effect [when]. Please check this matches your request, and tell us before then if anything needs to change.

Callback request

Thanks for asking us to call. A member of the [business] team will phone you [when] about [detail]. If a different number suits you better, send it here and we will update it.

Number change

Our team has confirmed this number request: [detail]. [business] will make the change [when]. Calls may pause briefly, so please tell us if that time is a problem for your office.

What to put in every confirmation

A good confirmation repeats the exact thing agreed, the date and time, and what the customer needs to do. For an engineer visit, that means access to the premises and someone to test the phones. For a number change, it means knowing calls might pause.

Ask the customer to reply if anything looks wrong. A confirmation that invites correction catches errors early and shows you care about getting it right.

Where confirmations go wrong

Watch for these common slips.

  • Sending a confirmation before a person has actually agreed.
  • Giving a window so wide the customer cannot plan around it.
  • Forgetting to mention that service may pause during a change.
  • Using a date format that could be read two ways.

FAQ

Can the agent confirm a number port?

It should not. A port needs a person to check identity and timing. The agent can collect the details, and then send this confirmation once a team member has agreed the date.

Should I confirm things the customer asked for in chat?

Yes. Repeating the request back takes ten seconds and avoids costly mistakes. It also gives you a written record if there is a disagreement later about what was agreed.

What if the customer wants to change the time?

Invite them to reply in the same chat. Then send an updated confirmation with the new time so there is only one current version of the plan.

More free tools for internet phone and small telecom providers

Read the guide: Answer set-up and call-quality questions for smaller telecom services.