Start here for a new setter referral.
amos.social/roadmap-callWelcome
Here's your day at a glance.
Reports and other alerts
AI responses
Read the conversation, make the reply yours, then approve or dismiss it.
Coaching conversations stay in Inbox for personal replies.
Appointments, availability and customer outcomes
Share a booking link
Choose the right call. The lead picks an available time on the Amos page.
Not sure which SOMA path fits?
amos.social/intro-callQuestions about the Vedic Hybrid course.
amos.social/book · Vedic discoveryExplore private mentoring with Sam.
amos.social/book · Mentoring discoveryBooking system status
One operational gate for the complete booking journey
Amos must pass booking, scheduling, communication and cutover checks before Calendly is retired.
Checking the native booking system…
Legacy Calendly import and rollback tools
These controls preserve old history during migration. They are not the booking system for new customers.
Contacts, lead pipeline and new enquiries
Filters & sort
Loading contacts…
Contact overview
Migration review · Identity and coaching checks
Loading migration review queues…
Loading pipeline…
Loading enquiries…
Plan your next email.
Recent drafts
Pick up where you left off.
Loading campaign drafts…
Campaigns stay as drafts. This workspace cannot send them.
Plan and review broadcasts without leaving Amos
Loading campaign drafts…
Campaigns stay as drafts. Sending is unavailable here.
Personal email pilot Preview only
Invite a few close students to reply
Choose each person individually, write a genuine personal note and review the exact consent, suppression, Broadcast, unsubscribe and reply path. This validates real correspondence without treating replies as a deliverability shortcut.
Search the complete contact directory. Suppressed and unconsented contacts are excluded.
No students selected yet. Search for a consented student above and tap Add to build the list.
There is deliberately no Send button. The final live pilot needs a separate approval after every check passes.
Understand who can receive marketing and why
Loading consent totals…
Loading audience options…
Suppression always wins
A contact is excluded if marketing consent is missing or incomplete, if they unsubscribed, or if a delivery event suppressed their address. A tag can never override that protection.
Choose the visual look your customer receives
Preview a layout, then use it for a campaign draft.
Loading automation email copy…
One timeline for delivery and engagement
Postmark setup, streams, safeguards and launch readiness
Delivery setup
Check the provider configuration and recorded safeguards.
Loading deliverability checks…
Loading server architecture…
Loading email routes…
Booking emails and the steps that need you.
Needs attention Checking attention…
Checking delivery attention…
Booking journeys
Open a booking to see its email timeline.
Loading booking records…
Booking emails only. Up to 20 bookings from the loaded records.
Not checked
Launch checks Not checked
Open to check recorded launch requirements.
Nurture eligibility
Open to check consent, timing and source evidence.
Challenge eligibility Not checked
Recorded app evidence only. This review cannot enrol or send.
Open to load eligibility evidence.
Client programmes and document locks
- 1Initial live session1 hour
- 2–4Video recordings3 × 2 hours
- 5Final live session1 hour with Sam
- 6/12hPurchased blockShared balance
- 30/60mClient choosesPer appointment
- ✓Outcome reviewThen deduct time
This view is read only. Each automatic flow keeps its own delivery gate.
Edit a workflow map. Saving never starts an automation.
These maps are drafts. Existing source and document locks still apply.
Choose a workflow to begin.
Choose any card in the journey map to edit its label, timing and action details.
One visual map, four independent approvals
Website booking capture is already owned by Amos. The remaining switches stay deliberately separate so one credential can never make everything live.
- 1Postmark transactional deliveryReplacement Live token + webhook proof
- 2Google Calendar + Meet writesOne controlled internal booking proof
- 3Paid access evidenceExact Stripe account and membership parity
- 4Journey approvalExact copy, documents, consent and owner sign-off
Loading…
Loading…
The conversations that closed and booked a course are the AI's best teacher.
The replies your team taught the AI. These shape every in-chat draft.
Teach the support assistant how to answer. In a SOMA Support chat, the AI drafts a reply for you to review and send (the same ✨ button), and it learns from every reply you send. Paste your FAQs, policies (refunds, cancellation, billing) and how-to answers here — this is its only source of truth, it will never invent a policy and will escalate anything it can't answer.
Loading…
Scan recent comments for rule matches
How to review & teach the bot
- The reply box is pre-filled from your rules. Edit it however you like.
- Wrong type of reply? Tap a Reclassify button (e.g. → reset) to swap to that response.
- Teach it: after reclassifying, tap a word under "Teach a trigger" (e.g. "affirmations") so similar comments auto-classify next time. Pick a distinctive word so it doesn't over-match.
- ✨ Draft with AI or Refine to reword; Shuffle for another template.
- Approve sends one reply immediately. Select ready replies, then Queue ready replies to post them safely in the background.
Tap Scan comments to pull recent comments and suggest replies. Review them, skip anything unsuitable, then approve one by one or queue the selected replies to post in the background.
Hands-off auto-posting of reset replies, every 6 hours
Status: …
The number amos is working to move
Auto-updates every Monday
Loading your weekly performance…
Learned from your real post performance, stored and growing
Tap Calculate to begin.
From your YouTube + Instagram comments
Tap Analyse comments or 💡 Reel ideas from comments to begin.
Proven reels worth re-posting
Tap Find picks to begin.
Competitor breakouts and niche trends, reframed for SOMA.
Loading the radar…
Script batches from Claude Desktop. Tap one to open it.
No batches yet. In Claude Desktop say something like "write me 3 sleep reels and save them" — each writing session lands here as its own batch.
Carousels and community posts, planned in Claude Desktop and saved here, ready to publish. Tap Publish on a row to add your slide images.
Choose your video and destinations. Review once, then share.
Need a reel idea?
Batch uploads & folder tools
Auto-find files: pick your videos folder once
Connections
The Instagram connection also enables receiving DMs in Conversations.
Reach check before posting
AMOS controls publishing and learning. These native choices still happen in each platform and materially affect how the post is packaged.
Review the caption for each destination you selected above.
TikTok Studio
AMOS does not auto-publish TikTok while the approval route is held. Check privacy, disclosure, cover and schedule inside TikTok Studio before posting.
Platform draft options
Posts now after confirmation.
amos posts the carousel with one shared caption (Instagram's only API option).
amos writes one caption per slide. Open Instagram, build the carousel from your photos, and paste each one (per-slide captions are an app-only feature).
Your content planning grid
Tools
Metric freshness
Publication labels use saved links and dates, not a live check of the social platform.
Powers the live call copilot. Create a key at deepgram.com, then paste it here.
Lets the Viral Lab pull your TikTok rivals' breakouts. Create a key at lamatok.com, then paste it here. Roughly £5 a month at your volume.
The main Soma App account. Blends its web subscriptions into the money view. Read-only pulls every 6 hours; Amos never writes to Stripe. A restricted read-only key works too.
Checks active, trial, past-due and memberships scheduled to stop after their paid period. No customer data is shown, no membership is imported and no Stripe object is changed.
Included: Soma App and Soma - SS APP. Excluded: Soma - System Scaling, Soma-meditation - Monzo and Test. Existing subscriptions stay in their current account. Suppression evidence, webhook parity and access parity must all pass before any cutover.
Loading the local membership parity review…
Off: you create this content in Claude Desktop (your subscription), so amos doesn't spend the metered API on it. Operational AI (DM & support drafts, comment replies, lead triage, call copilot) always runs.
Loading…
Upload SOMA light/dark lockups, marks, email-header artwork and app-icon source in the dedicated visual library.
One organised home for every approved SOMA brand asset.
Uploading stores and previews artwork only. It does not publish to the SOMA website, change outgoing email artwork, deploy files or send anything.
Light and dark surfaces
Preview SOMA artwork against both surfaces here. Website and email activation remains a separate reviewed step.
Loading previews…
Asset library
Use the supplied transparent PNG lockups and canonical SVG marks. SOMA's wordmark should never appear without its mark.
Loading asset slots…
Replacing or removing an active asset never deletes the previous original from Storage, so it can be recovered.
Checking connections…
Only admins can connect or reconnect services. Setters automatically use the workspace connections they have permission to access.
Checking…
📋 Payload reference (for your developer)
POST JSON to the URL above. Always include appUserId (the same id used for that member's app messages) and the secret. No message text is needed for a subscription-only update.
Checking…
No events compared yet. Comparisons appear once RevenueCat starts sending events.
Revenue, engagement and the at-risk worklist live on their own page:
Setup steps (for your developer)
- RevenueCat → Project → Integrations → Webhooks → Add new.
- URL: the Webhook URL above. Environment: Production.
- Authorization header: paste the exact Authorization value above (generate + Save it here first).
- Events: INITIAL_PURCHASE, RENEWAL, CANCELLATION, UNCANCELLATION, EXPIRATION, BILLING_ISSUE, PRODUCT_CHANGE, NON_RENEWING_PURCHASE, SUBSCRIPTION_PAUSED.
- Confirm entitlements are
base,premium,vedic premiumand the app callsPurchases.logIn(firebaseUid)(so RevenueCat's app_user_id matches amos). - Leave amos in shadow for a few days, watch the parity readout, then Go live.
Live SOMA app revenue, engagement and retention. Admin only.
Sales operating metrics separate operating metrics
Reset funnel page → signup → practice
RevenueCat the official numbers
Are we growing or leaking?
Money collected
App engagement
Trials to convert all active free trials
Revenue at risk who to save first
Choose when appointments can be booked. Standard sessions have at least 18 hours’ notice; discovery calls use their own notice rule.
Current appointments keep their booked time. Google Calendar conflicts and the saved availability rules are checked together before a new time is accepted.
Checking legacy connection…
Loading your app content…
Loading…
Cost per trial, CAC and ROAS by ad
Loading…
Signed in as —
amos build —
These options change only your experience. Team access, lead assignment, and shared conversation rules stay controlled by an admin.
Read activity on this tab
Conversation, message and profile-booking listeners only. These callback counts are not billed reads. Counts stay in this tab and reset when you sign out or reload.
Checking Facebook sign-in…
This only changes how you sign in to Amos. To connect the SOMA Page or Instagram, use the separate connections in Content → Publish.
1. In your authenticator app (Google Authenticator, Authy, 1Password) choose “add account → enter a setup key”, and paste this key: