Agenting, told as three jobs

Agenting means the agent does the operation. It hears the conversation, decides the next step, acts in your systems, and leaves a record. These stories are the examples in the overview. They are not published customer results.

Home monitoring

The call comes in after the shift

A patient on a home monitor needs help, and the team has gone home.

The overview’s example is Medicare-approved home monitoring for patients 65 and older. A person handles support, outreach, and compliance calls. After hours, that coverage drops.

The phone rings at night. The agent answers. If it is a device problem, it stays on the line and works through tech support. If the call is outreach, a compliance reminder, or someone who might become a patient, it takes that job instead of handing the person a closed office. When the call ends, the agent writes the summary into the CRM and flags anything a person still has to see.

1. HearsA phone call for support, outreach, a compliance reminder, or a new lead.
2. DecidesWhich of those jobs this call actually is.
3. ActsStays with the caller and finishes that job, including after the shift.
4. RecordsWrites the summary to the CRM and flags what needs a person.

Service pauses

Pause service from Friday

An email or a voicemail asks for a pause. Nobody should have to retype it.

Patients ask to pause service by email and voicemail. Staff open each message, search the CRM, and key the dates in by hand.

A voicemail says, “I need to pause service from Friday.” That line is an example, not a customer quote. The agent reads the voicemail, or the email that says the same thing. It finds the patient, sets the pause dates, and updates the CRM. If the dates do not fit the rules, it does not guess. It flags the exception.

1. HearsThe email or the voicemail asking for a pause.
2. DecidesWho the patient is, and whether the dates fit.
3. ActsSets the pause and updates the CRM.
4. RecordsLeaves the change in the record, or flags the request when it does not fit.

Facility management

The owner’s message does not sit in the inbox

A tenant or an owner writes. The agent reads it, files it, and alerts someone when it matters.

Tenant and owner emails and voicemails wait on a person. Staff read each one, find the unit or the tenant, and update the system by hand.

An owner sends a message about a unit. The agent reads the email or the voicemail and works out what is being asked. It finds the right record, updates the CRM, and sends an alert when a person needs to act. The inbox is not a pile left for the morning.

1. HearsAn email or voicemail from a tenant or an owner.
2. DecidesWhat the request is, and whether it needs an alert.
3. ActsUpdates the CRM and sends the alert when it matters.
4. RecordsThe message is no longer only in the inbox. It is in the system.

Request a pilot