A caller reached the closed-line message

What it looks like#

The caller reaches the number, hears one short sentence naming the business, and the call ends. In the workspace there is a call record with a reason — the line is off, or it is outside hours — rather than a conversation. No transcript, because nobody was invited to speak.

It is worth being precise about what changed. This used to be a bare refusal that the worker answered by deleting the room: the caller heard the call connect and immediately drop, and no record existed at all. The refusal now comes back as a brief carrying the message, the worker synthesises it, plays it on a track of its own, records the refusal and hangs up.

What it means#

Line off

Somebody switched the line off. It answers, says so, and ends. Nothing is broken.

After hours

The call arrived outside the hours set on the line. Hours live on the line record alongside its purpose and permissions.

Budget refused

The workspace's cap for paid work is spent. The refusal is asked before the call is answered, and a refused inbound call gets the spoken message rather than silence.

All three end the call with a reason on the record, which means the difference between them is readable afterwards. That matters more than it sounds: "we were closed" and "we were over budget" call for entirely different responses from a business.

What the message says, and what it deliberately does not#

The closed-line message is deterministic — the same sentence every time, in the business's own name — and it is warmed alongside the greetings so an out-of-hours caller hears it immediately rather than waiting for it to be produced.

It carries no opening hours. A fixed sentence that names a time is wrong the moment the hours change, a holiday is added, or a caller in another timezone hears it, and a message that confidently states the wrong thing is worse than one that states less. If callers need to know when to ring back, put that where it can be kept current rather than in a warmed audio line.

What Connect completed#

• Answered the call, spoke the refusal in the business's own name, and ended the call cleanly.
• Created a call record with the specific reason — line off, after hours, or budget — rather than an unexplained short call.
• Kept the caller's number, so somebody can ring back deliberately.
• Warmed the message ahead of time, so the refusal was immediate rather than preceded by a pause.

What Connect did not complete#

• No conversation was held, so there is no transcript, no summary and no lead.
• No call-back was scheduled. The refusal is not a promise, and Connect does not create commitments the caller was never offered.
• The caller was not told when the line reopens, because the message deliberately carries no hours.
• Nothing was queued for a person automatically. A run of after-hours calls is worth looking at, and looking is a decision somebody makes.

What you can do#

1. Read the reason on the call record before changing anything.

   Result Off, after hours and over budget look identical to the caller and need different fixes.

2. If it should have been open, check the hours on the line rather than the engine.

   Result Hours sit on the line record with its purpose and permissions; the engine has nothing to do with them.

3. If callers arrive out of hours regularly, count them.

   Result A handful is noise; a pattern is either the wrong hours or a real demand for cover.

4. Ring anyone back whose call mattered.

   Result They heard a refusal, however polite; a call-back is the only thing that repairs that.

What an administrator can do#

• Set or correct the hours on the line, and check the timezone they are interpreted in.
• Switch the line back on if it was turned off for a release or a test and never restored.
• Adjust the message text on the Phone screen's behaviour settings, which both audiences have.
• Review the workspace's cap if refusals are budget-driven rather than time-driven — a line that closes because the budget is spent looks like a line that is closed.

When to escalate#

Escalate if the closed-line message plays during hours the line is definitely open, or if it plays with no reason recorded at all. The first is a configuration or timezone fault; the second is a refusal that is not one of the three known kinds and should be looked at properly. Bring the times of the calls and the hours the line is meant to keep.

Questions#

Related#

• Connecting a phone line, end to end
• Inbound phone call, end to end
• The call connected and nobody spoke
• SMS in Connect
• Troubleshooting