Skip to main content

SC Phone Number Register

What this is: every telephone number Symphony Core owns in the live sub-account (vOyZYmChRuyjFM0yUtba), what each one is for, and how each is configured. It exists because a number's role changes faster than the documents that mention it, and a document that restates the digits goes quietly wrong when it does.

The rule this register carries: an operational document refers to a number by its role and links here. It does not restate the digits. The exception is a document whose purpose is to be the record of that number — this register, the advertised-number entry in Company Info, and the caller's own profile.

What this register is not. It does not govern what may be published. One number is advertised and one only, and that decision lives in Symphony Core Company Info, which deliberately prints no number that may not go on public material. This register is the internal operating view: it includes numbers that must never appear on a deck, a page or a signature.


1. The numbers​

NumberFriendly nameRoleWho dials from it
+1 (475) 244-9646Symphony CoreThe advertised company line. The only number on published materialNobody. It places no outbound calls
+1 (475) 323-6565Brian (surname TBC), stale: the live label still names the second placement, who left before 2026-11-09. Rename it to the role in the UIThe inside-sales caller's prospecting line. Every cold dial, and the number prospects call back. It stays with the role across placements, so callbacks from prospects already dialled from it reach a personWhoever holds the inside-sales seat, named in the Contractor Registry Vame entry, "Placed VA". Never resolve the caller from this label
+1 (475) 323-6801gettextbackproSee §4 — the live label and the documented role disagreeNobody

The SC Testing sub-account holds a separate number for sandbox work. It is recorded in the SC GHL Sub-Account Inventory, not here, because it belongs to a different sub-account.


2. Configuration of record​

Read live from the sub-account UI on 2026-10-29. The connector exposes no phone-number settings operation, so every row here is a UI read and there is no script that can monitor it — see inventory §8.

+1 (475) 244-9646+1 (475) 323-6565
Default numberYesNo
A2P 10DLCVerifiedVerified
1st priority routeNone. The team-member route was removed 2026-10-29Team Member — the inside-sales caller, Web App + Mobile App
Voice AIErica, and she is the primary, not a fallbackNot set
Incoming timeout15s20s
Outgoing timeout27s20s
Backup after timeoutVoice AI (Erica)Voicemail
Call recordingOnOn
Recording announcementOn — "This call will be recorded for quality purpose"On — "This call will be recorded for quality purposes"
Call ConnectOffOn
Whisper messageOn — "Call From {{contact.first_name}}"Off
Connect to contact (outbound)Immediately after they answerImmediately after they answer

The backup is a radio, not a list. A number falls back to Voice AI or to voicemail, never both. That is why the caller's line and the company line behave differently, and why the company line cannot also take a voicemail.

"Ring more Team members" on the caller's number holds an inactive entry for the founder — the chip is present, the checkbox is off, so it does nothing. Left recorded rather than removed, because an entry that does nothing is worth knowing about before someone wonders why it never rang.


3. The recording announcement, and what is still owed​

This is the only row in this register that a legal position depends on. The SC Outbound Calling Compliance Standard §5 withdrew the caller-spoken disclosure on the strength of these announcements. Both numbers have the setting on, which is what makes that position tenable.

The announcement does not appear on the recording, and that is expected — the platform plays it before recording begins. Absence of the announcement from a recording file is therefore not evidence that it failed to play. That inference was made the wrong way round on 2026-10-29 and produced a false stop-the-line finding; the rule it left behind is that nothing is concluded from what a recording does not contain without a second source.

Owed, and not yet resolved. Both numbers set Connect me to the contact (Outbound calls) to Immediately after they answer. The adjacent option is named After the Call Recording Message finishes, and it is not selected. On its face that is a setting which bridges the caller to the prospect without waiting for the message to complete.

Until a test call settles it, this register records the setting and claims nothing further. The test: dial a mobile the tester holds from the caller's number, answer it, and say nothing — either the announcement is heard before the caller's voice, or it is not.


4. +1 (475) 323-6801 — a known disagreement​

Live, the number is labelled gettextbackpro and has no documented role in the prospecting motion.

Canon describes it two other ways: as the Voice AI demo line throughout the Event Networking Playbook, and as "Test Admin 1" in SC Test Accounts. The disagreement is already logged as finding F-4 in the 2026-08 prospecting sprint backlog.

This register records what is live. Resolving which role the number actually serves is a separate decision and is not taken here.


5. Changing a number's role​

A number's role is not a configuration detail; it is the thing other documents depend on. When one changes:

  1. Update this register first, including the live-read date.
  2. Search canon for the digits before assuming the change is done. A number reassigned without that sweep leaves instructions pointing at the wrong line — in October 2026 the caller's new prospecting number was still described in five documents as a testing line that must never reach a prospect.
  3. Check the compliance standard if the number places outbound calls. Reputation, recording and the calling window all attach to the number, not to the person.
  4. Record it in the operational change log.

One live trap, left deliberately visible. Two draft automation specs — the SMS testing PRD and its Twilio architecture doc under docs/projects/automation/ — still use the caller's number as a test fixture, including in assertions that send messages to it. Both are draft and nothing is built, so there is no hazard today. Anyone building from them must swap the fixture first, or the test suite will text a live prospecting line.



Document History​

VersionDateChanges
1.22026-11-12The line belongs to the role, not to a person. The friendly-name column still named the second placement after the third took the seat, and the daily call-log review routine read the label to decide whose folder its report belonged in: on 2026-11-11 it filed the current caller's review in the departed caller's folder. The row now says the label is stale and that the current holder comes from the Contractor Registry. The live label itself is a UI change, still owed
1.12026-11-02The caller's line changes hands. +1 (475) 323-6565 reassigned when the first inside-sales placement resigned; kept with the role rather than retired, so callbacks from the 47 prospects already dialled from it reach a person. The §5 sweep this register demands was run and found the drift it was written to catch: the C-024 spec still named the line a sandbox testing number and told readers to put it on a test fixture, two days after it went live to prospects. Corrected there. The voicemail greeting remains in the previous caller's voice until re-recorded
1.02026-10-29Created. Written the day the inside-sales caller was given her own prospecting line and the company line became Voice-AI-only, because the reassignment left five documents describing her new number as a testing line prospects must never be called from. Carries the live configuration of both active numbers, the recording-announcement position and the outbound-connect question still owed against it, and the disagreement over +1 (475) 323-6801