Anyone at a client's business texts theStacc what happened, and it turns up on their Google profile, social, blog or website after the owner says yes.
For owners, crews and contractors who text instead of logging in, and for our account managers. The design rests on one rule: theStacc's number is the front door, but only the owner approves.
How it works
- Anyone texts the number. Cody, a contractor nobody had met, sends 11 photos from a city procurement matchmaker. theStacc thanks him and holds the files.
- The owner confirms the sender once. Dev gets "Is Cody Hale with you?" and replies YES. Cody becomes a contributor: he can send, never approve. If Dev says no, the files are deleted.
- One question, then a proposal. theStacc asks only what changes the copy (was it Tue 10 Nov?), picks 4 of the 11 photos, and proposes 4 outputs: LinkedIn, Facebook, a Google update and a website block. It says what it won't claim: no contract, no customers.
- Approve by text. YES approves the idea. Each draft then comes back with its exact text and photo; YES, EDIT or "use the podium photo". Bigger batches open a no-login review link.
- The modules do the work. Photos land in Library, the idea in Content Hub, drafts in Local SEO and Social. The WordPress website block becomes a task for Meera's team.
- One honest receipt. LinkedIn and Google live with links, Facebook scheduled Thu 12 Nov, website pending with Meera's team until Fri 13 Nov. Cody gets a short thank-you.
- Facts take their own path. "Closed Thanksgiving" becomes an exact change (Thu 26 and Fri 27 Nov closed), approved by Dev, applied on Google and confirmed.
- Approvals come in stages, at a human pace. Idea, then each draft, then the time, then the live link. A Google post is ready in minutes, a blog post in about 30, a website block in 2 working days. Drafts finished overnight wait until 8 am; a waiting draft gets two reminders at most, then Meera; after 7 days it expires and nothing posts.
- theStacc also texts first. A weekly photo ask (easy to skip), new reviews with a drafted reply, lead alerts with their source, the monthly plan and the monthly receipt with a Proof Score.
What it is and isn't
What's in it
- SMS and email in the US, WhatsApp in India
- Sender matching and contributor roles
- Content path, fact-change path, private path
- Approve by reply and a no-login review page
- Receipts, nudges, review and lead alerts
- Account manager inbox, group threads optional
- MCP tools for Claude and GPT users
Not in this version
- A mobile app, iMessage, RCS
- Publishing anything an owner hasn't approved
- Autopilot for texted material
- Agent edits on WordPress sites (a task instead)
- Customer-facing reels and ads while Video Studio and Ads are team only
Release order
| Phase | What ships |
|---|---|
| A | US pilot, 5 to 10 clients: one Twilio number, email in, sender matching, content path to Google and social, approve by reply, receipt, account manager inbox. Fix the three bugs first: Google posts replacing the client's photo, Must include dropped, autopilot approving inbound ideas. |
| B | Holiday and special hours by text, review and lead alerts, weekly nudge, website tasks with status, the review page. |
| C | WhatsApp for India (after written OK from Meta), group threads, monthly plan by text, Proof Score, MCP tools. |
| D | Reels from texted video when Video Studio opens; free-form chat through the Assistant. |
Still to decide
- Approve by reply, or always the review link? Recommended: YES for one fully shown item from the owner; the link for anything bigger.
- Group threads in v1? Recommended: optional per client, 1:1 by default. A thumbs-up in a group approves nothing.
- One shared number or one per client? Recommended: one per client in the pilot, about $1.15 a month each; routing and groups get simpler.
- Who adds website blocks on WordPress sites, and how fast? Recommended: Meera's team, within 2 working days, shown as pending until live.
- Drafts one at a time, or a morning digest? Recommended: one at a time at first; owners can switch to one 8 am digest.
- Standing OK for routine posts? Recommended: later, one narrow type at a time (e.g. Google updates from crew job photos), each with a text and UNDO for an hour.
- Can office staff approve fact changes? Recommended: only when the owner delegates that action type.
- WhatsApp go-ahead? Recommended: written confirmation from Meta or the provider before building.