Identityidentity.authtoolkit.comStatic preview

identity.authtoolkit.com

Demo Companies

Plain-English workflow examples showing how agencies, bot sellers, voice-agent builders, and product creators can use AuthToolkit foundations.

Demo Companies

Demo Company Workflows

Plain-English examples showing how agencies, bot sellers, voice-agent builders, and product creators can use AuthToolkit foundations without hunting through the console.

These examples show workflows and jobs to be done. They help builders see how products connect without exposing internal architecture.

Static demo-company examples only. No live API wiring, real credentials, live customers, real product execution, billing, or integrations are connected.

Who This Helps

Plain English

Non-coders

See the setup path without learning internal systems.

Agencies

Explain client setup, access, plans, testing, logs, and readiness in one story.

Vibe coders

Start with a working foundation path before building product features.

Bot and voice-agent sellers

Package client projects, keys, plan access, testing, logs, and health.

SaaS builders

Use shared setup surfaces as the base for product growth.

QR experience builders

Connect scan experiences to access, entitlement, logs, and readiness.

Fake Demo Companies

Examples

LeadBot Studio

Demo
Voice-agent and bot packages for local businesses.

LeadBot Studio sells voice agents and chat bots to local businesses.

Customer: Local service businesses that want missed-call follow-up, lead capture, and customer communication.

Problem: The agency needs to manage client projects, protect access, issue safe keys, control plan and usage access, test actions, inspect logs, and check setup health.

AuthToolkit fit: AuthToolkit gives the agency a shared foundation for access, keys, entitlement, testing, logs, health, and help.

Bright Bake Co.

Demo
Simple QR-powered customer experiences for a small bakery.

A small bakery wants a simple customer experience powered by QR codes and future plan-controlled features.

Customer: Small retail shop.

Problem: The bakery wants scan-to-experience flows, customer access context, plan-aware features, logs, and readiness checks.

AuthToolkit fit: AuthToolkit connects QR Experience, Identity, Commerce, Logs, and Health into one understandable setup path.

Metro Tutors

Demo
Protected access and simple plan checks for tutoring clients.

A tutoring business wants protected client/student access and simple plan checks.

Customer: Tutoring teams serving parents and students.

Problem: The business needs parent and student access, verified contact details, plan checks, action testing, logs, and health.

AuthToolkit fit: AuthToolkit connects Identity, Commerce, Verification, Notification, Logs, and Health for a safer client experience.

Demo Restaurant Group

Demo
QR experience setup, plan access, logs, and readiness for restaurants.

A restaurant group wants QR experience, ordering-related setup, plan access, logs, and health.

Customer: Multi-location restaurant operators.

Problem: The group needs a restaurant project, QR experience, product access, entitlement checks, scan/action previews, logs, and readiness.

AuthToolkit fit: AuthToolkit gives the restaurant group a workflow for QR Experience, Commerce, Identity, Logs, Health, and optional growth products.

Workflow Examples

Use cases

LeadBot Studio sells a $99/month voice-agent package

The agency needs a clean way to explain client setup, access, plan checks, testing, logs, and readiness before live wiring.

  1. Create a client project.
  2. Review environment and integration settings.
  3. Review key and scopes.
  4. Check whether the client plan allows the feature.
  5. Test a voice-agent action.
  6. Inspect logs to see what happened.
  7. Review health before going live.
  8. Use Page Help when confused.
IdentityCommerceLogsHealthNotificationAnalyticsQR ExperienceMarketing

Outcome: The agency can explain, test, and troubleshoot the client setup before live wiring.

Bright Bake Co. adds QR experiences with plan access

The bakery wants QR scans to open a hosted customer experience with plan-aware features later.

  1. Customer scans a QR code.
  2. The hosted experience opens.
  3. Identity provides access context.
  4. Commerce checks whether the plan allows the feature.
  5. Logs show the scan and action path.
  6. Health shows what is ready or blocked.
QR ExperienceIdentityCommerceLogsHealthAnalyticsMarketing

Outcome: The bakery can understand the QR setup path before adding live integrations.

Metro Tutors protects client and student access

Parents and students need protected access, verified contact details, and simple plan checks.

  1. Parent or student account is created.
  2. Contact details are verified.
  3. Commerce checks plan entitlement.
  4. Test Console previews access.
  5. Logs explain the result.
  6. Health shows readiness.
IdentityCommerceVerificationNotificationLogsHealthAnalytics

Outcome: The tutoring business can explain protected access and plan checks without exposing internals.

Demo Restaurant Group reviews QR experience readiness

The group wants QR experience setup, product access, action preview, logs, and readiness.

  1. Create the restaurant project.
  2. Review QR experience setup.
  3. Check product access and entitlement.
  4. Preview a scan or action.
  5. Inspect logs.
  6. Review health.
QR ExperienceCommerceIdentityLogsHealthNotificationAnalyticsMarketing

Outcome: The group can understand the QR experience path and what to fix before live work.

LeadBot Studio Setup Path

Primary flow
1

Create a client project

Start with a clear Project ID and setup values for the client package.

Project SettingsIdentity
2

Review environment and integration

Check the selected environment, app connection, routes, and setup context.

Console Settings
3

Review key and scopes

Preview which key type and scopes match the client package.

Key CreationIdentity
4

Check plan access

Confirm the feature is allowed by the client plan before testing.

Commerce
5

Test a voice-agent action

Preview the request, response, scope check, and entitlement check.

Test ConsoleIdentityCommerce
6

Inspect logs

Use trace IDs and timeline events to understand what happened.

Logs
7

Review health

See what is ready, warning, blocked, or demo-only before live wiring.

Health
8

Use Page Help

Ask page-scoped questions when the setup path is unclear.

Page Help

How Products Connect

Jobs

Identity

Protect access

Controls who can use the client or project setup.

KeysTest ConsoleLogsHealth

Commerce

Control plans, usage, and upgrade-required states

Lets builders package and sell features safely.

Console SettingsTest ConsoleLogsHealth

Verification

Decide verification truth

Helps confirm email, phone, or future customer checks.

NotificationLogsHealth

Notification

Deliver messages

Sends email, SMS, or push but does not decide verification truth.

VerificationLogsHealth

Logs

Understand what happened

Explains test and action results with trace IDs and timeline.

Test ConsoleHealth

Health

Know what to fix next

Shows ready, warning, and blocked states.

LogsConsole Settings

QR Experience

Add scan and hosted experience workflows

Lets builders connect physical QR use cases to platform setup.

IdentityCommerceLogsHealth

Marketing

Send campaigns when allowed

Campaign actions should respect Commerce entitlement and consent boundaries.

CommerceAnalyticsLogs

Foundation Stack

Path
Project

The client or business workspace.

RequiredEnvironment

Development, staging, or production context.

RequiredIntegration

The app or backend connection preview.

RequiredKeys / Scopes

Safe key previews and product access planning.

RequiredCommerce Entitlement

Plan and feature access awareness.

RequiredTest Action

Static request and response preview.

RequiredLogs / Trace

Trace IDs, decisions, and timeline preview.

RequiredHealth

Readiness, issues, and next actions.

RequiredPage Help

Page-only explanations when users get stuck.

Optional

What Builders Gain

Outcome

Explain the setup

Builders can show clients what exists before live work begins.

Start with one product

A team can begin with Identity or Commerce and add more products later.

Test before going live

Static tests make the planned request, response, entitlement, logs, and health easy to understand.

Troubleshoot calmly

Logs and Health make the next issue visible without exposing secret internals.

Boundaries

Static

Fake demo companies

These examples are fictional and do not represent real customers.

No real customer data

All names, plans, actions, and paths are static examples.

No live product execution

Actions are previews only.

No live billing

Commerce examples explain plan and entitlement awareness only.

No live voice-agent integration

LeadBot Studio shows the setup story, not a connected voice-agent provider.

No QRVerse live wiring

QR Experience examples remain static and do not connect to QRVerse live systems.

No Knowledge Hub search

Page Help and future helper boundaries remain static in this phase.

No replacement claims

The examples explain AuthToolkit workflows and do not claim to replace any third-party platform.

Suggested Actions

Next
Read User ManualOpen LeadBot Studio ExampleReview Project SettingsReview Console SettingsOpen Test ConsoleInspect LogsReview HealthRead Page Help

Video Story Ideas

Future

LeadBot Studio: Setting up a voice-agent package

Show client project setup, keys, plan checks, test action, logs, health, and help.

Project SettingsConsole SettingsKey CreationTest ConsoleLogsHealth

Bright Bake Co.: QR experience with plan access

Show QR scan workflow, Identity access context, Commerce entitlement, Logs, and Health.

Console SettingsTest ConsoleLogsHealth

Metro Tutors: Protected client access and verification

Show parent/student access, verified contact, plan checks, logs, and readiness.

Project SettingsTest ConsoleLogsHealth

Demo Restaurant Group: QR experience, logs, and readiness

Show restaurant project setup, QR experience, entitlement, action preview, logs, and health.

Console SettingsTest ConsoleLogsHealth