Welcome
Here's your day at a glance.
Appointments, availability and customer outcomes
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
Loading migration review queues…
Loading contacts…
Loading pipeline…
Loading enquiries…
Create, review and understand every customer email in one place
Your campaigns, customer journeys and delivery health
Amos manages the audience and experience. Postmark handles the infrastructure underneath once the Live server is approved.
Build a campaign without the technical clutter
Choose the right consented audience, write the email, review its customer view and keep it as a draft until the launch checklist is complete.
- 1DesignLook, subject and message
- 2AudienceConsent is enforced
- 3ReviewLight, dark and mobile
- 4LaunchLocked until approved
Postmark stays under the bonnet
Transactional messages and marketing broadcasts remain separated. Bounces, complaints, opens, clicks and unsubscribes will return to Amos after the webhooks are approved.
Loading campaign drafts…
Plan and review broadcasts without leaving Amos
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.
Loading campaign drafts…
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
Beautiful, consistent emails without designing from scratch
Start with a branded visual layout, preview it on desktop or mobile, then write the campaign. Every design is intentionally lightweight for reliable inbox rendering.
Loading automation email copy…
One timeline for delivery and engagement
Postmark setup, streams, safeguards and launch readiness
The email engine behind Amos
Credentials stay on the server. Amos gives you the campaign experience, contact history and safety controls without sending you into provider settings for daily work.
Loading deliverability checks…
Loading server architecture…
Loading email routes…
See exactly what happens after every booking
One booking, one clear path
Amos keeps the booking, communication and outcome together so you can see what the customer experiences before anything is made live.
- 1Booking capturedContact + appointment + slot lockWorking
- 2Calendar & Meet preparedQueued only after verified payment; external creation stays off in Safe ModeReady
- 3ConfirmationExact customer email generated for reviewDraft
- 4Reminder24-hour timing shown in the customer timezoneDraft
- 5OutcomeComplete, no-show or follow-up chosen by youHuman check
Loading journey ownership…
Loading draft automations…
- 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
Checking nurture safeguards…
Every observed app user is included or blocked with an exact reason. This view cannot enrol or send.
Checking authoritative app evidence…
Edit revisioned draft maps for discovery calls, Vedic students, SOMA Elite appointments and source-locked nurture without creating an execution path.
Design, inspect and preview the exact journey a customer experiences
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.
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.
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
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. GHL DND reconciliation, 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.
This week's bottleneck the one number to fix
The pipeline reels → app
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
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.
1. In your authenticator app (Google Authenticator, Authy, 1Password) choose “add account → enter a setup key”, and paste this key: