Clara in the team's group text

One group thread with Clara in it: what it takes and what we prove first. For Fede's decision.

2026-11-04 · Clara coworker lane · Proposed, pending review · origin: Miriam Gallegos (Situs) started a group text with Clara at 8:57 AM MT

What happens todayGroup modeOptionsWhat we buildHow we prove itDecisions

What happens today

Clara's number can only talk to one person at a time. A group text reaches her as if the sender wrote alone, and her answer goes back to that sender only.

TODAY (NOV 4, 8:57 AM MT, SITUS) Miriam (PM)starts the group Lee, Deibyleasing agents, in the group Carriersplits the group per number Clara's Situs linesees "Miriam → me", nobody else Clara's reply goes to Miriam alone. Lee and Deiby saw the question, never the answer.
What Miriam saw. She asked "any showings today?"; Clara answered her correctly ("none"), one to one, and explained that replies come back on the same thread. Her teammates were left out.

Group mode: the same number, kept together

Our texting provider has a second mode for the same number. A group message creates one shared conversation with every member in it; Clara answers once and it lands in the group on every phone.

GROUP MODE (PROPOSED) Miriam, Lee, Deibyone group thread on their phones Provider keeps the grouptells us every member's number Clara: one conversationeach member known by their role one reply, seen by everyone in the group One-to-one texts keep today's path untouched: the number's normal door still fires; the group door only acts when there are 3 or more in the room.
Limits. Local numbers only (Situs +1 720 740 4240 and the Fairhaven test line qualify; toll-free lines do not). At most 10 people in a group, Clara included.
Options, what we build, proof, decisions

Options

OptionWhat the team getsCost / riskVerdict
A. Group mode on the existing lineA real group thread with Clara in it. Anyone asks, everyone sees the answer.One settings change on the number at the provider (Fede's go). Open mechanic to prove first: one-to-one texts must not double up.Recommended
B. A second texting vendor for groupsSame as A.New vendor, new number per customer, new carrier registration, two texting stacks.No
C. No group threadEach teammate texts Clara directly (works today). Clara can send the team a morning showings summary.None.Fallback until A is proven

What we build (option A)

New capability, so it ships dark behind one company setting, "Clara joins team group texts", default off. Fede turns it on per customer.

#PRWhat it does
1The group doorReceives a group conversation from the provider, maps each member to a person by their role at the company. An unknown number is "someone on the team", never guessed. Ignores anything with fewer than 3 members.
2The group turnThe staff desk runs on the group as one conversation: every member's role in context, one reply to all, same tools, same rules (identity by roles, no string rules on "did they ask Clara").
3The line settingFlips the provider setting on one customer's number. Written only on Fede's go, Fairhaven first.

Staff keep hearing from Clara's line, shared with prospects, per the Nov 3 ruling. Two Situs cells need to be on the right records first (Lee's and Deiby's); without that, Clara would see two strangers in the room.

How we prove it

  1. Fairhaven first: two test phones and the Fairhaven line in one group. Ask "any showings today?"; the answer must appear on both phones in the same thread.
  2. Same group, a one-to-one text from one phone: Clara answers once, on that phone only, no duplicate from the group door.
  3. Only then Situs: Fede turns the setting on; Miriam's own group is the first real run.

Decisions for Fede

  1. Build option A dark (three small PRs, nothing a customer sees until turned on)? Recommend yes.
  2. Put Lee's and Deiby's cells on their records now, so group mode knows them on day one? Recommend yes.
  3. Meanwhile, tell Miriam each teammate can text Clara directly? Recommend yes, Clara already said so.

Sources: provider docs on group texting (long codes only, 10 participants, autocreated conversations with every member; the number's own door still fires). Related: coworker hub, group texts section.

PropFlow Docs