Phone and messages

What it does

This is the part of Rufio that talks to people — the calls that come in while you're under a sink, the ones that need making back, the emails that need writing, and the record of every one of those conversations so the next person to pick up a thread isn't starting from nothing.

Two of these need something connected before they can run at all. Incoming calls and outbound calls both need setup first — a phone number has to be connected before Rufio can answer or place anything. This is not a limitation you work around; it's a thing to connect once. Until it's connected, call handling doesn't work, and Rufio says so rather than failing quietly.

Email drafts, the communication paths behind them, conversation history, and the follow-up that comes out of a conversation are the settled part of this page — they work without any connection step and are the part to build a habit around first.

The phone side is at an earlier stage than the messaging side, on top of needing a number connected. Support requests are in the same position: the records and the routing work, but this is newer ground than email and it's still being filled in, so expect more change here than elsewhere.

Support requests, the follow-up and assignment attached to them, and the records and context behind them are covered where your kind of business actually has support requests to handle. A business fielding warranty or after-service callbacks has this; one whose customer contact is all pre-sale may never touch it.

When to use it

• A call comes in while you're on a job. With a number connected, Rufio answers rather than letting it ring out, takes what the caller needs, and leaves you the conversation and the follow-up rather than a missed-call notification.
• You've got a list of people to ring back. Ask what's outstanding and you get the callbacks with the reason for each, not just the numbers.
• An email needs writing and you'd rather not write it. Ask for it and the draft comes back with the history behind that customer already accounted for.
• Someone asks "what did we tell them last time?" The conversation history answers it directly, across calls and messages both, rather than you searching two places.
• A customer has a problem with work already done. The support request holds the thread, who it's assigned to, and what's happened so far.

How to use it

Ask for what you want in a sentence — draft a reply to a particular email, ask who needs ringing back, ask what was last said to a customer about a warranty.

For calls, the setup step comes first and is one-time. Once a number is connected, incoming calls are handled according to the rules you've set rather than a default you didn't choose.

Example — a call that comes in outside working hours:

Request: nothing asked in the moment — the phone rings after hours.

What Rufio does: with a number connected, it takes the call rather than letting it ring out, captures what the caller needs, attaches it to the right customer — creating the record if they're new — summarizes the conversation, and prepares the follow-up for the morning.

Where it stops: it doesn't commit you to a time. Rufio can hold a slot with the caller, but confirming the booking follows the rules you set and defaults to asking you. You come back to a prepared callback and a summary, not a diary someone else filled in.

This work starts at Suggest, like everything else does on day one — Rufio prepares the reply or the callback and waits for your explicit OK before it goes anywhere. Message drafting is one of the tasks that commonly moves to Review within weeks, meaning Rufio sends and then shows you what it sent. Call handling is worth thinking about separately from message drafting when you set these levels, because a live caller and a draft email are different kinds of risk, and the levels are set per kind of task rather than together. Autonomy levels covers how that works.

Parameters

What Rufio needs from you. For calls, a connected phone number — that's the setup step, and nothing on the call side runs before it exists.

For the rest, context about how you want to sound and what you don't want said. The useful instructions here are the boundaries: what you'd rather handle personally, which customers you always want to speak to yourself, what shouldn't be committed to over the phone. Those are worth saying once rather than correcting repeatedly.

Corrections carry forward. Rewrite a draft and the change is kept as a rule for similar messages later, so the next draft starts closer to how you'd have written it.

For support requests, what matters is who handles what. Rufio can assign and route, but which of your people owns which kind of problem is something you tell it rather than something it infers.

What you get back

From a call, the conversation itself handled and the follow-up left for you — what the caller wanted, what was said, and what needs doing about it, attached to the right customer rather than sitting in a separate inbox.

From a message request, a draft. It waits for you at Suggest, and that's the point of the level rather than a gap in the feature.

From a history question, the actual thread — calls and messages together, in order, against the customer they belong to.

From a support request, the record with its assignment and its context, so the next person to open it knows what's already been tried.

Limits

Rufio does not commit you to work on a call. It can hold a time slot with a caller, but confirming the booking follows the rules you set and defaults to asking you — that boundary is in Limits and boundaries, and it's a hard line rather than a setting you can talk it out of.

Calls do not work without a connected number. No amount of autonomy changes that, and Rufio will tell you it can't rather than appearing to work.

It does not sign or agree to anything on your behalf in a message. Agreements are drafted, never executed.

It does not invent a new way of handling calls because it noticed a pattern. New behavior is proposed to you in plain language before it exists.

This page doesn't own what happens to the content of those conversations once stored — see Your data for where it lives and who can reach it.

Related

• Customers and sales — the customer records and deals these conversations attach to
• Work and scheduling — what happens when a caller wants a time slot
• Your data — where conversation history is kept and who can read it
• Autonomy levels — why call handling and message drafting deserve different levels
• Limits and boundaries — what Rufio will never do on a call
• Every capability — the full list, including which of these need setup first