Skip to content

Your phones know who is calling.

Communications is the phone, chat, mail and file system in The One Stack, the platform MSPs run their whole business on. It gives an MSP’s team a cloud phone system, an AI receptionist, team chat, business mail and file sync that read the same client record as the service desk. It replaces your phone system, team chat, hosted mail and file sync.

A full cloud phone system, team chat and business mail live on the client record. The caller is matched before anyone picks up, a missed call becomes a ticket, and a text thread sits beside the queue.

Replaces: your phone system, team chat, hosted mail and file sync.

Harbor ITMeridian LawSample data

Communications

Phones, text and chat on the client record
Dana Whitfield
Meridian Law · matched before pickup
AnswerSend to THEO
Today
CallAnswered by THEO, Meridian LawT-4821 opened
VoicemailTranscribed, Northwind DentalT-4816 opened
TextCascade Financial: add a user MondayIn thread
Chat#meridian-law: call summary postedFrom THEO
Caller context
Open ticketsT-4821 · T-4815
DevicesMER-WS14 · MER-FS01
ContractManaged Complete
Last contactText thread, yesterday

Illustrative product view with sample data.

The job, start to finish.

The work Communications carries, in the order it happens, and where it hands off.

  1. 01

    Ring

    A client calls your main line. The call enters the call flow you designed: business hours, menus, queues, and the place where THEO sits.

  2. 02

    Caller match

    The number matches a person, and the person matches a client. Their company, open tickets and recent calls, texts and voicemails are on screen before anyone picks up.

  3. 03

    Answer or THEO

    A technician answers with the record in front of them. Or THEO answers, confirms who is calling and asks what is wrong.

  4. 04

    Ticket

    The call becomes a ticket with the caller and the company on it. When a runbook covers the request, THEO runs the fix during the call. Outside its runbooks it hands the call to a person.

  5. 05

    Summary

    After the call, the transcript and a summary are saved with the call, and the ticket shows the contact’s recent calls. Nobody writes up the call from memory.

Inside Communications.

A few of its screens. Every module page shows its own.

The caller, before you answer

While the phone rings, the softphone shows who is calling, their company and their open ticket. The call list beside it shows which calls were missed and which ones THEO wrote a recap for.

Phone system

Illustration, sample data. An incoming call shows the caller, her company, her open ticket and her recent contact before anyone answers.

A call THEO took

THEO confirmed the caller, opened the ticket and ran a runbook that covers the request. The transcript and summary stay with the call, and the follow-up went to a technician on the service desk.

AI receptionist

Illustration, sample data. A call THEO took: the transcript, the summary, the ticket it opened and the handoff to a technician.

Chat on the same record

A message in a channel became a ticket where it sits. The ticket and the server it is about are linked in the conversation, and THEO answered a question about the server in the channel.

Team chat

Illustration, sample data. A channel message turned into a ticket, with THEO answering a question about the server in the same conversation.

What it hands to the other systems.

The caller is matched to the client record

Before anyone picks up, the phone number resolves to a contact and a company on the record your sales and account work already uses.

Sales and accounts

A missed call becomes a ticket

When nobody answers, the service desk opens a ticket with the caller and the company on it. The call is not left in a call log for someone to find.

Service desk

A text thread sits beside the queue

A client’s text to one of your numbers opens a thread your whole team can read and answer, next to the tickets they are working.

Service desk

A chat message becomes a ticket

A message in a channel turns into a service desk ticket in place. The conversation stays where it is, and the ticket carries the message.

Service desk

The fix runs on the device during the call

When THEO has a runbook for what the caller describes, the runbook acts on the caller’s device while they are still on the line, and each step is recorded.

Scripts and automation

A phone fraud signal reaches detection and response

Signs of fraud on a phone line are sent to detection and response (Defend), where they sit with the rest of the security events your team reviews.

Detection and response

What changes for you.

For owners

Your phones, chat, mail and files stop being separate vendors with separate client lists. They also become apps you sell: Workspace and Files at a price you set, and phone service invoiced in your brand, with The One Stack as the carrier of record.

MSP owners

For technicians

You see who is calling and their open tickets before you answer. A missed call arrives as a ticket, a text arrives as a thread, and the calls THEO’s runbooks cover are handled before they reach you.

Service managers and technicians

For co-managed IT

A client’s internal IT team works the same tickets that calls create, limited to their own company. A co-managed person has a phone line when you assign one, and sees the company’s files in your portal.

Co-managed IT

Proof slot

A customer running Communications on The One Stack

A named MSP, the tools it retired for this system, and a quote approved in writing by the customer.

Switching to it.

What imports

Your phone numbers are ported to the platform, so clients keep dialing the numbers they know. A client’s files in Dropbox move into Files with the migration service on /switch/migrate, one client at a time.

Bring your data

What runs side by side

Build and test your call flows on a new number while your current phone system keeps taking calls. Move one number, then the rest. Chat, mail and files start with your own team and go client by client.

Run side by side

What you turn off

Once the numbers are ported and your team works in the new chat, mail and files, you turn off the old phone system, the team chat subscription, the hosted mail service and the file sync tool.

How switching works

Questions

Questions about Communications

Is it a full phone system?

Yes. Phone system (Voice) is a full cloud phone system with extensions, queues, call flows, softphones, desk phones, text messaging, fax, voicemail and recording. It reads the same client record as your service desk, so the caller is matched before anyone picks up.

Can THEO answer the phone, and what does it do?

Yes. THEO answers, identifies the caller, opens the ticket, and runs the fix on the call when a runbook covers it, and outside its runbooks it hands the call to a person with the details on the ticket. THEO never places emergency calls, which are for people and handsets.

Does THEO have to answer every call?

No. You design the call flow, and you decide where THEO, menus, queues and people sit in it.

How is phone service charged?

Phone usage is metered, on top of a plan priced by people and devices. See /pricing for how the plan and metered usage work.

Can I sell phone service, mail and file storage to my clients?

Yes. Phone service, Workspace and Files are client apps you sell under your name, described on /client-apps. Workspace and Files are sold at a price you set, and phone service is invoiced in your brand, with The One Stack as the carrier of record.

Do my clients and I keep our phone numbers?

Yes. Existing numbers are ported to the platform, so callers keep dialing the numbers they know.

Start

Run on One.

Start a trial and bring one client across, or book a walkthrough and follow a call down the line with us.