Text theStacc mock ยท example data

Text theStacc: every back-and-forth

Clients, their crews and our own team text theStacc's number. These 67 screens show the conversations as they look on the sender's phone, with what theStacc did behind each one. Example data for Prairie Oak Flooring (Wichita) and Brightsmile Dental (Pune), both fictional. The whole feature is new; 37 screens are tagged for notable extra backend work.

Skim all screensShort versionCoverage One at a time with arrow keys or Play, or all on one page

What this shows

1A. First contact: who is sending

The trigger case: a contractor nobody knows texts 11 photos.

TX01Cody's first text: unknown senderNeeds backend workMMS burst grouping (10 + 1 photos arrive as two messages); held-intake store with short retentionTX02Dev confirms CodyTX03Dev doesn't know the senderTX04Contractor who works for two clients

2B. Content path: material becomes posts

TX05Proposal for the matchmaker photosNeeds backend workClaude triage call (picks photos, destinations, the one question); Suggested idea written to Content HubTX06Approve one post by replyTX07Swap the photoTX08Receipt to the ownerNeeds backend workPublish status reconciliation: each output is marked live only when the platform returns a link; the website block stays pending until someone checks the live siteTX09Cody's receiptTX10Crew lead sends a finished jobTX11Photos too dark, screenshot instead of originalNeeds backend workImage quality check: brightness, blur, and screenshot detection (status bar, low resolution)TX12Voice note becomes an FAQ ideaNeeds backend workSpeech to text on the voice note; transcript stored with the idea as provenanceTX13Short video sentNeeds backend workVideo understanding (Gemini) picks timestamps; frames exported as stills into the LibraryTX14Offer: 15% off LVP

3C. Fact changes

Hours and services skip the content workflow.

TX15Thanksgiving hoursNeeds backend workGoogle special hours merge (holiday hours added without touching regular hours); read-back to confirm Google accepted themTX16Site and Google disagreeNeeds backend workSite crawl diff against the Google profile; conflicts raised as one question eachTX17New service

4D. theStacc texts first

TX18Weekly nudgeNeeds backend workScheduler with quiet hours; nudge skips or rewrites itself when the person already sent that week; backs off when ignoredTX19New 5-star reviewTX202-star review goes to a personTX21Lead alertTX22Monthly plan by textTX23Monthly receipt and Proof ScoreNeeds backend workRival snapshot from public Google profile data, stored with the check date

5E. Safety and the private path

TX24"Don't use the photo with the house number"Needs backend workAsset restriction propagates to Library, scheduled posts, drafts and ideasTX25Complaint goes to a personTX26"Cancel"TX27STOPNeeds backend workOpt-out registry checked before every outbound message on every channelTX28Contributor tries to approveTX29Group threadNeeds backend workGroup MMS (Twilio Conversations): per-participant identity on every message

6F. Other channels and our own team

TX30Email with full-size files and a Drive linkNeeds backend workInbound email parsing; Google Drive public-folder fetch; duplicate photo check against the LibraryTX31WhatsApp: dental camp in PuneNeeds backend workWhatsApp Business API (24-hour window, quick-reply buttons); Google event post and Instagram schedulingTX32Sales texts call notesNeeds backend workTeam-number recognition; prospect record created from notes; Claude extraction of facts and ideasTX33Teammate idea across clientsTX34Claude user sends through MCPNeeds backend worktheStacc MCP server: suggest_from_material tool, scoped to the signed-in contact's project and role

7H. What gets published

The finished posts, as customers see them, each traced back to its thread.

PO01LinkedIn: matchmaker postPO02Facebook: matchmaker postPO03Google update: matchmakerPO04Website block previewNeeds backend workAccount-manager task for WordPress sites; status turns live only after a person checks the live URLPO05Derby job: Google and FacebookPO06Offer: Google and InstagramPO07Blog: "From the crew" sectionPO08Review reply and quote cardPO09Google hours for ThanksgivingPO10Dental camp: Google event and story

8G. Behind the scenes in theStacc

AP01Account manager inboxAP02Content Hub idea from a textAP03Settings: texting contactsNeeds backend workProject texting contacts with role and channel; per-action delegation; nudge schedule with back-offAP04No-login review pageNeeds backend workSigned, short-lived link bound to Dev's number and to this exact version of each draftAP05Proposed Google changesNeeds backend workProposed-change queue in front of Update on Google; Google special hours merge and read-back check

9I. Timing and step-by-step approvals

Generation takes minutes, Google takes hours, people take days. Each stage gets its own approval.

TM01The clock for one sendNeeds backend workQuiet-hours queue: drafts finished between 8:00 pm and 8:00 am wait and go out at 8:00 am or later, local timeTM02Blog post: outline first, then 30 minutesNeeds backend workLong-running generation job with a promised time and a follow-up text when it finishesTM03Step by step, then the owner goes quietNeeds backend workReminder and expiry scheduler: one reminder a day, two in total, hand-off to the account manager, expiry at 7 daysTM04Morning digest instead of one at a timeNeeds backend workPer-owner setting: drafts one at a time (default) or one morning digestTM05Photos sent at 2 amTM06Google turns a post downNeeds backend workPlatform rejection reasons mapped to plain-language fixes; a changed draft goes back to stage 2TM07Google takes time on an editNeeds backend workProfile edit status polling: applied, under review, showingTM08Standing OK for routine postsNeeds backend workStanding-approval rules: narrow scope (sender, photo source, platform), per-post notice with a 1-hour undo

10J. More examples

MX01Award certificateNeeds backend workPDF reading (issuer, year, category pulled from the certificate)MX02New hire, with his OKNeeds backend workConsent recorded on the Library photoMX03A homeowner sends her photoNeeds backend workOne-time sender (customer) matched from the owner's heads-up; location data stripped from the photoMX04Price changeNeeds backend workSite text search across the client's pages; dated website taskMX05Hiring postMX06Press mentionNeeds backend workLink fetch and article reading (quote extraction tied to the source URL)MX07"How are we doing?"Needs backend workInsights summary by text (posts, leads, Google calls, rank) for a date rangeMX08Competitor ad screenshotNeeds backend workScreenshot read as a style reference (private, never posted); ads request routed to MeeraMX09A customer question becomes an FAQNeeds backend workQuestion routed from a team member to the approver; FAQ task with the approved wordingMX10WhatsApp: receptionist sends, doctor approvesNeeds backend workWhatsApp template message when the approver's 24-hour window is closed; contributor vs approver routing