① Capture & refine
Drop or paste (⌘/Ctrl+V) — photos, screenshots, emails, .txt/.md/.csv. Text fills the box; images attach.
③ Queue
Approved tickets file to the LIVE Pure Board (pure_board via mcp_intake, review-gated) with a local mirror, and slot into the easiesthardest queue. Drafts & revision requests stay here until resolved.
— tap preview —Sample address only — won’t receive until DNS + backend is set up
— tap preview —Sample number only — won’t receive until a Twilio line is provisioned
Don’t email/text these yet — they’re sample addresses to show the format. Emailing one bounces (NXDOMAIN) because in.acquisto.biz has no mail records. Going live = DNS + an inbound service (tickets t-email-intake / t-sms-intake). Until then: paste or upload here.
How email-in & text-in will actually work
Email-in (≈1 hr setup, mostly free): add an MX record for in.acquisto.biz Cloudflare Email Routing (or SendGrid/Postmark inbound). Incoming mail hits a small worker parses subject + body + attachments runs the Claude refine drops a draft into this queue. The tickets-xxxx@ token identifies the sender.
Text-in (Twilio): buy a number (~$1.15/mo), point its inbound-SMS webhook at a serverless function (Cloud Run / Supabase edge / Netlify fn). Texts (and MMS photos) function Claude refine draft in this queue, and it texts back “Got it — ticket created.” Same path the SMS-approval flow (t-sms-approve) uses. Full scope in INTAKE-CHANNELS-SCOPE.md.
Text-in (Twilio): buy a number (~$1.15/mo), point its inbound-SMS webhook at a serverless function (Cloud Run / Supabase edge / Netlify fn). Texts (and MMS photos) function Claude refine draft in this queue, and it texts back “Got it — ticket created.” Same path the SMS-approval flow (t-sms-approve) uses. Full scope in INTAKE-CHANNELS-SCOPE.md.