Why Connect Your Phone Line to Your Support Desk?

The follow-up gap

Picture a small business with a phone line and a shared inbox for customer issues. A customer leaves a voicemail asking about an order. Someone listens to it between two other jobs, thinks "I'll deal with that after lunch", and carries on. The voicemail is now a memory in one person's head. If they are off sick on Thursday, or the afternoon fills up, the customer waits and eventually phones someone else.

Nobody was careless. The phone system had the message and the support desk had the process for tracking work, but the two did not talk to each other. The only bridge was a person retyping a name and a number, which is exactly the kind of small job that gets skipped on a busy day.

What changes when they talk to each other

• The message becomes a work item. A "Create MapleDesk ticket" button on the voicemail makes a ticket with the caller, number, time, length, extension and transcript already filled in, and the recording attached.
• It has an owner. If the extension is linked to a person, the ticket is assigned to them. That link is set once, when you set up the extension.
• It happens once. A second click, or a colleague clicking on the same voicemail, opens the existing ticket instead of creating a duplicate.
• Tasks work the same way. If your team plans its day in MapleTask rather than in a ticket queue, the same voicemail can become a task for the same person.

Calling and texting back from the ticket

The other half is the reply. Once the work item exists, the person handling it usually wants to ring the customer. From a MapleDesk ticket there are two buttons, Call and Text. They appear only when two things are true: your account has MapleReceptionist, and the ticket's person has a valid phone number on file, either on the ticket or on their linked contact record.

"On file" is deliberate. If a customer writes "call me on 506-555-0123" inside an email, that number is not in the record. The ticket shows a small reminder, and the buttons stay hidden until someone saves the number properly. We would rather have one extra click than an agent dialling a number that was typo'd inside a sentence.

Text opens a drafted message you can edit before you send it. It goes from your account's own MapleReceptionist number, and the call or text is logged on the ticket, so the next person who opens it can see what already happened.

Where this does not help

• If nobody works the queue. A ticket nobody reads is just a voicemail in a different place. Connecting systems does not create the habit of checking them.
• If you get very few voicemails. For a handful a week, an inbox and a good memory may be enough. This pays off as volume and the number of people involved grow.
• If the extension is not linked. Without the link there is no owner to assign, so the buttons do not appear.

Automatic tickets: use with some care

There is an optional setting that turns every new voicemail into a ticket on its own. It is off by default. It suits a line where every message is real work. It is a poor fit for a line that also collects wrong numbers and sales calls, because the queue fills with noise and people stop trusting it. Many teams will prefer the button, where a person decides what is worth tracking. If you do turn the automatic setting on, only voicemails that arrive afterwards are handled; your old ones are left alone.

A sensible way to start

1. Link each extension to the person who normally answers for it.
2. Use the button for a couple of weeks and notice which voicemails you actually turn into tickets.
3. Only then decide whether the automatic setting is worth switching on for some extensions.

If MapleDesk or MapleTask cannot be reached at the moment you click, you will see a short message and the voicemail stays exactly as it was. See what is connected and what is not for the full list.