— FAQ
The cross-cutting questions we get on every demo call — pricing, channels, integrations, the agency tier, security, the rest of the suite. Industry-specific questions (real estate, healthcare, salons, restaurants, fitness, home services, political) live on the dedicated industry pages, linked at the bottom. If yours isn't here, a real person reads contact.
Most owners are live and capturing leads in under 30 minutes. Pick a template that matches your industry, change the wording to your voice, paste the one-line widget snippet on your site. The bot is live the moment the page reloads. There's no integration project, no onboarding fee, no calendar invite to a kick-off call.
No. The flow builder is a drag-and-drop visual canvas — drop a question, drag a connection, set a condition. The widget install is one line of JavaScript pasted into your site's footer or theme. If your site has a "header/footer scripts" box (most do), that's where it goes. Owners with no engineering team ship Alma every day.
Any site you can paste a JavaScript snippet into. That covers Squarespace, Wix, WordPress, Webflow, Shopify, Showit, GoDaddy, custom HTML — basically every modern website builder and any hand-built site. If your platform supports a "header" or "footer" code injection box, the widget works.
Sign up with an email, browse the 161 industry templates, click "Use this" on the one that matches your business. The flow loads pre-built. Tweak the questions to your voice (your services, your hours, your area), hit publish, paste the widget. Most accounts go template → tweak → publish in under 30 minutes.
Yes — 14 days, no credit card. You sign up with an email, build bots, capture real leads. We email you on day 10 to ask which tier you want. If you don't pick one, the account moves to read-only — your data and flows stay put — until you do.
Anyone who completes a conversation with one of your bots and gets captured as a contact — name, phone, email, or whatever fields the flow asked for. People who start a conversation but bounce don't count. You can archive old subscribers at any time to free up room without losing the underlying transcript.
Bots keep running. We don't shut down a live conversation mid-sentence. You'll see a warning in the dashboard around 80% and again at 100%, and any overage is billed at the end of the cycle at the tier's per-message rate. If you're consistently over, that's the sign to move up a tier — and the upgrade prorates the same day.
Upgrades take effect immediately and prorate against your remaining cycle. Downgrades take effect at the next billing date so you keep the limits you paid for. Switching annual to monthly (or vice versa) is the same — current cycle finishes at the rate you're on.
Both are listed on every tier card. Annual saves about 17% — pay once, run for the year, no per-month invoice noise. Monthly is the lower-commitment shape; switch annual at any renewal. Both flavors get the same product, same templates, same support.
Yes. You sign up with an email, build bots, capture real leads. We email you on day 10 to ask which tier you want. If you don't pick one, the account moves to read-only — your data and flows stay put — until you do. No card on file means no surprise charge on day 15.
Published refund policy lives at helloalma.chat/refund-policy. The short version: monthly plans are pay-as-you-go and stop on cancel; annual plans get a prorated refund of unused months minus the discount you took. If something's wrong, email alma@huntercreativemedia.com with "Refund Request" in the subject and a real person responds.
For the full tier breakdown — Starter $29, Growth $79, Agency $199, Enterprise — see the pricing page.
The website widget, full stop. One snippet of JavaScript on your site and the bot is live — the same page, the same surface every visitor already lands on. That's the only channel we'll ask you to buy Alma for, and it's the only one we'll claim is shipping.
The integrations are built. They're sitting in Meta's platform-approval review and have been for about two months — that's the whole story. We don't have an ETA we trust enough to publish, and we're not going to invent one. Every account today deploys to your website. The moment Meta approves us, Messenger and Instagram light up across every existing tier with no upcharge.
That's the design. The flow builder produces one graph; the deploy step picks which channels it ships to. When Messenger and Instagram come out of the development queue, the same flow you're already running on your website will render on every surface — same questions, same branches, same lead inbox. You build once, you deploy everywhere we ship.
Alma is a chatbot for the website. SMS is a different category of tool — outbound campaigns, two-way reply, carrier compliance, 10DLC registration — and it's CampaignCNX+'s job inside the suite. The two pair cleanly: the lead lands in Alma, gets pushed into CampaignCNX+ as a contact, and the SMS drip handles follow-up. One account, two products.
14 days, no credit card, full access to every template and every feature. The fastest way to answer the rest of your questions is to use the product for an afternoon.
Email/SMTP on every tier. Google Sheets, Zapier, CampaignCNX+ SMS push, CoreCNX contact + timeline events, and generic outbound webhooks starting on Growth. Webhooks are signed (per-endpoint secret) and retry-safe. The list is short on purpose — we ship what works and don't claim integrations we don't actually have.
Not natively. There are no native connectors to HubSpot, Salesforce, Follow Up Boss, Pipedrive, GoHighLevel, ActiveCampaign, or any of the named CRMs. The bridge is Zapier or a webhook your IT contact wires up — both work, both are documented, and almost every modern CRM has an inbound endpoint. If you're already on CoreCNX (the suite's CRM), the contact + timeline push is native.
Same answer: no native integrations to Calendly, Mindbody, Acuity, Square Appointments, Boulevard, Vagaro, Dentrix, Eaglesoft, Open Dental, Athenahealth, ServiceTitan, Housecall Pro, etc. The bridge is the outbound webhook + Zapier path. The bot collects the request; your existing system holds the source of truth. We're a marketing-layer chatbot, not a chart system or a calendar.
Yes — REST API access ships on the Agency tier and Enterprise. Endpoints cover workspace management (GET /api/v1/agency/workspaces, POST /api/v1/agency/workspaces), template deployment (POST /.../deploy-template), lead pulls, and webhook configuration. Starter and Growth tiers don't include API access — those tiers ship the dashboard, the templates, the integrations panel, and Zapier.
Every outbound webhook is signed with a secret you configure per endpoint. Your receiver verifies the signature before trusting the payload. Retries are retry-safe — if your endpoint times out and we retry, you won't get a duplicate write. Standard pattern, documented in the integration panel, no surprises.
Yes. Each conversation can fan out to as many destinations as you want — email the lead to your front desk, append a row to a Google Sheet, push the contact into CoreCNX, and fire a generic webhook to your internal tool, all on the same completion event. The fan-out is configured per flow, not per account, so different bots can route differently.
Operators running Alma for multiple clients — agencies, consultants, fractional CMOs, marketing teams that manage a portfolio. One parent account, sub-account workspaces per client, white-label on the widget and email-from, and the REST API to script onboarding. $199/mo for 20 active bots pooled across all client workspaces.
It's 20 active bots total across the whole agency account, pooled — not 20 per workspace. So if Coastal Realty needs three bots and Mindful Yoga needs one and Coastal HVAC needs two, you've used six of your twenty. Same logic for the 50,000 subscribers and 100,000 messages — those are pooled across every workspace under your agency parent. If you need more, the Enterprise tier lifts the caps.
Yes. You can issue a workspace-scoped login to your client's marketing lead — they sign in, they see only their workspace, they don't see the agency parent or any of your other clients. Most agencies skip this and keep the workspace managed, but the option is there for clients who want the seat.
Three things on every Agency account: the domain the widget loader serves from (CNAME to a subdomain on the client's own domain), the branding inside the widget chrome (logo, palette, bot avatar, bot name — Alma's mark removed), and the email from-address on lead notifications (leads@yourclient.com instead of an Alma address). The flow builder UI inside the agency dashboard is not white-labeled — that's only seen by your team.
Yes. If a client outgrows the managed-service relationship and wants to run Alma on their own, we'll convert the client workspace into a standalone Alma account on whichever tier matches their volume. The conversation history, lead exports, flow graphs, and widget config all come with the workspace — nothing is rebuilt, nothing is deleted, and the agency stops paying for it.
Yes — REST API access ships with every Agency-tier account at no add-on cost. Spin up a workspace, deploy a template, pull leads, configure webhooks, all from your terminal or a build script. Most agencies wrap workspace creation and template deploy in a five-line shell script and onboard new clients in three minutes.
For the full agency walkthrough — workflow, pricing math, white-label scope — see the agency page.
Conversations are isolated per workspace — no other account can see your data, ever. Encrypted at rest, TLS in transit. Standard data export and deletion supported on request. You decide retention windows and what fields each flow collects. Industry pages spell out the specifics for healthcare and political contexts.
Out of the box, no. Alma is a marketing-layer chatbot for your public-facing website — PHI lives in your PMS or EHR, not in a website widget. A Business Associate Agreement is available on the Enterprise tier; talk to sales for the regulated setup. We won't claim "HIPAA compliant" on a marketing page just because we encrypt at rest, because that's not what the term means. The healthcare page covers this in detail.
Data export and deletion are supported on request — that covers the core operational requirements of both. Conversations are workspace-isolated, so a deletion request scopes cleanly to one account. If you operate under either regime and need a Data Processing Addendum, that's part of the Enterprise conversation; email sales and we'll route it.
US-based hosting on standard cloud infrastructure. If your operation has a specific regional-residency requirement (EU, Canada, UK), the Enterprise tier is where we discuss data-region options — talk to sales. We'd rather give you a specific answer scoped to your situation than overclaim a region we can't guarantee for every account.
The full answer lives in the privacy policy — see privacy.html. Short version: Alma is a flow builder, not an LLM-driven product — the bots run scripted flows you authored, and there's no model being trained on your customer conversations as the default product behavior. If you have a specific question about a specific workflow, email alma@huntercreativemedia.com and we'll answer plainly.
No. Alma works standalone — most accounts run it that way. The siblings (Beacon for field operations from $59/mo, CampaignCNX+ for SMS from $0.06/message, CoreCNX for CRM from $49/mo for 5,000 contacts) are independent products that share an account when you want them to. Pick one, pick all four, mix and match — the billing follows the products you actually turn on.
CoreCNX is the spine — when it's on, it holds the unified contact timeline, and Alma pushes lead-capture events into that timeline as they happen. CampaignCNX+ pulls contacts out of CoreCNX for SMS sends. Beacon writes door-knock and field-event data back into the same timeline. Without CoreCNX, each product runs independently and exports to wherever you tell it to (Sheets, Zapier, your own CRM).
Yes. Alma doesn't require CoreCNX. The lead from a chatbot conversation can land in your existing CRM via Zapier or webhook, and Alma never touches CoreCNX on that account. The same is true for the other suite products — each one supports the bring-your-own-CRM path.
Suite-bundle pricing exists for accounts running two or more products. The math is per-account, not per-product — talk to sales with the shape of your operation (number of bots, SMS volume, contact-list size, field team count) and we'll quote a bundle that beats stacking the standalone tiers.
For how the four products fit together, see the suite page.
161 templates across 17 categories — real estate (23), home services (21), healthcare (18), fitness & wellness (15), salons & spas (14), restaurants (12), education & coaching (11), political (10), plus 9 more verticals (pet care, financial services, automotive, legal, retail, e-commerce, professional services, nonprofits, B2B). Every template ships on every plan — there's no premium-template gate.
Fully. A template loads as a starter graph in the flow builder — every node, every branch, every action is editable. Change the wording, add a question, remove a step, swap out the destination, redirect a branch. The template is a starting point, not a fixed shape.
Yes. Open a blank flow, drop a START node, add question and action nodes, wire up the branches. Most accounts start from a template and edit; some start blank because their use case is unusual. Both produce the same artifact and ship the same way.
Inside an Agency account, yes — agencies clone a flow they built for one client into another client's workspace in two clicks, which is most of the day-to-day operating pattern. Cross-account template sharing (one Alma account publishing a template another Alma account can install) is on the roadmap; today, the path is export-and-import the flow JSON via the API.
— Still didn't answer your question?
If your question is on this page, the answer is on this page. If it isn't — and the question is industry-specific or use-case-specific in a way the generic FAQ can't cover — head to the dedicated industry page below or send it to contact. The same small team that builds Alma reads the inbox; you'll have a reply by the next business day, and it'll be a real one, not a templated thanks-for-reaching-out.
— Start free
Sign up, pick a template, paste the widget. Most owners are live and capturing their first qualified lead before they finish the FAQ on a competitor's site.