How it works

A tracked path from requirements to access.

FreedomBot is designed for self-serve onboarding without hiding operational dependencies. Every stage has a persisted record, a next action, and an exception path.

01

Configure

Validated answers produce the smallest suitable active tier and a persisted module scope.

02

Activate

The portal starts Stripe Checkout for the setup fee and monthly plan when Stripe is configured.

03

Authorize & intake

DocuSign completion and operating inputs determine when provisioning can begin; there is no built-in signing fallback.

04

Provision

A queued job creates workspace access; status and failures remain visible to operations.

Your portal is the source of truth

Every client gets a private portal. It answers two questions: where am I and what’s next.

  1. Started
  2. Learning about FreedomBot
  3. Choosing modules
  4. Reviewing plan & price
  5. Awaiting payment
  6. Payment received
  7. Awaiting agreement signature
  8. Awaiting intake
  9. Intake complete
  10. Setting up your FreedomBot
  11. FreedomBot is live
  12. Payment processing
  13. Payment canceled

Implementation scope

What is configured—and what remains your responsibility.

The system is an operating layer. Good inputs, explicit owners, and professional review remain necessary.

Business context

Offers, priorities, brand language, process inputs, workflow owners, and escalation expectations provided by your team.

Workflow structure

Module scope, repeatable steps, handoffs, status communication, approval points, and planning cadence.

Ongoing stewardship

Your team keeps source information current, reviews sensitive outputs, maintains connected accounts, and owns final decisions.

Integrations and controls

Concrete controls, without certification claims.

FreedomBot does not currently claim a compliance certification. Production security also depends on deployment, provider configuration, and your access practices.

Stripe

Hosted Checkout manages configured payment collection; FreedomBot stores identifiers and status needed for onboarding.

DocuSign

DocuSign provides agreement signing when configured. A verified Connect event—not a portal return page—authorizes the intake stage.

Email and SMS

SMTP and optional Twilio delivery are controlled by environment settings. Attempts and errors are recorded for operations.

Application controls

Portal/admin access, server-side validation, stage history, job flags, and environment-managed secrets provide the current control foundation.

FAQ

Straight answers.

Do I have to book a demo?

No. The product is self-serve. Start and pay from the site and portal, complete the agreement through configured DocuSign signing, then provide intake details. If DocuSign is unavailable, onboarding pauses at the agreement stage.

How long does setup take?

The application can move through configuration, payment, a DocuSign agreement, intake, and provisioning without a sales call. Actual timing depends on complete inputs, working provider integrations, and whether the setup needs review.

Which integrations are supported?

Stripe Checkout, SMTP email, Redis/Celery jobs, and optional Twilio SMS are part of the current platform. Availability depends on valid credentials. Additional business-tool integrations must be explicitly scoped.

What if something fails?

Automation errors can create an operations flag and notification record. Recovery may require an operator; the failure remains visible rather than being presented as success.

Can I change plans later?

Package records drive the public catalog and can sync to Stripe when that integration is configured. Subscription changes after purchase may require operational support depending on billing state.

Does FreedomBot provide legal or financial advice?

No. Legal and finance modules organize context, workflows, review points, and reminders. Licensed professionals remain responsible for advice and regulated decisions.