Maintenance state has not been confirmed by the operations backend.
Choose what you would like to do.
Only use this if you do not already have a CreateJourney account. Business and Personal are setup types, not separate login pages.
Enter the details printed on the back of your SmartBoard. Your board will be securely linked to your account after registration.
Choose what fits you best. You can still use all CreateJourney features either way.
Start with the basics. You can customize everything else later.
Your board is linked securely to your account after verification. If you registered without a board, continue without activation.
Use the words that make sense for you.
Choose up to 3 customer or visitor actions. Shorter Journeys usually perform better.
Tell CreateJourney where each action should take people.
Welcome to CreateJourney. Your first board and Journey are connected and ready.
Here's what's happening today.
Prototype dataJourney AI is building enough SmartBoard history to identify a reliable revenue opportunity.
Get help with your board, Journey or setup.
Securely connect the services Journey AI can work with.
Connections use provider authorization. CreateJourney never asks you to store a Google, Instagram, Facebook or email password inside the dashboard.
Provider passwords are never collected here. Production OAuth tokens must live server-side, use minimum permissions, and be revocable by the owner.
Review permissions before authorization.
Choose the business account or page you want CreateJourney to use.
Choose what Journey AI is allowed to read and what it may prepare for future approved actions.
Journey AI can use this connection as context only when you enable access below.
Give Journey AI the context it needs to become a useful business partner.
Start with the basics. Journey AI will use this context across your workspace.
These details help future content look and sound like your business.
Give Journey AI enough detail to answer useful questions and create relevant work.
Pick any goals that matter. You can change them later.
This helps Journey AI give advice that fits the way your business actually works.
Review what Journey AI will use as business context.
Your business memory, AI work, creative assets and action center.
Journey AI is building a working understanding of your business.
Choose a starting point. Journey AI will take you to the right tools without making you hunt through the workspace.
One organized home for Journey AI conversations, highlighted topics, decisions, images, campaigns, projects and generated work. Journey AI maintains the organization so you do not have to dig through chat history.
Important ideas, recommendations, business facts and follow-ups surfaced from your Journey AI activity.
Generated graphics, uploaded logos, SmartBoard creatives and social assets.
Clean conversation cards with titles, last activity and a quick way to resume.
Key decisions and important operating notes separated from ordinary conversation.
Work threads, marketing plans and campaigns grouped together.
Choose how many image concepts Journey AI should normally create and how much it should ask before generating.
Save operating facts, lasting decisions and guardrails. Pin the most important items so Journey AI treats them as high-priority context.
Journey AI uses the business type, saved knowledge, CreateJourney activity and approved connected-account context to surface useful next moves. Recommendations say whether they are observed, learned, business-informed or experimental.
Proactive ideas are specific to this business. Journey AI will not invent performance patterns it cannot support with available data.
Every conversation remains part of the Journey AI archive. Important facts, ideas, decisions, tasks and future leads are additionally organized here so they can be found later.
Prepare branded social graphics, promotions and SmartBoard end-screen images. Generated files are saved into the Journey AI Media Library when the secure creative backend is available.
Journey AI prepares work first. Publishing, messaging, provider updates or other consequential external actions require the correct role, approved provider permission and explicit approval.
Journey AI can prepare the message, creative, SmartBoard experience and connected-provider drafts together. Nothing is published, sent or changed externally without the required permission and approval.
Tell Journey AI the outcome you want. It will keep the campaign specific to this business and avoid unsupported claims or invented offers.
Each pack shows what Journey AI can prepare for that provider and whether secure execution is currently available.
It compares approved campaign and Journey results against recorded baselines, separates correlation from proof, and only increases confidence when enough evidence exists.
Business-specific patterns appear only when supported by actual measured data.
When evidence is weak, Journey AI can suggest a controlled test instead of presenting a guess as fact.
Turn business goals into coordinated campaigns without making the owner manage a pile of marketing tools. Journey AI uses the business profile, brand, actual performance evidence, approved connected accounts and prior results to recommend what to do next.
Recommendations are business-specific and disclose whether they come from observed data, learned history, business knowledge or a proposed experiment.
Describe the result you want. Journey AI prepares a plan, content and channel actions for review.
Campaigns, content and scheduled actions are connected here so the owner can see the work without jumping through multiple tools.
Journey AI uses these guardrails when creating ideas and remembers them for future marketing work.
Create one idea and adapt it for social media, Google Business, email, website content and SmartBoard screens. Journey AI keeps the message consistent while formatting each channel appropriately.
Choose a starting point or describe exactly what the business needs.
Previewed text remains a draft until it is added to a campaign, SmartBoard or external action.
Prepare a variant or choose an existing item.
Plan marketing in one place. Calendar entries can be prepared locally, but actual future publishing or SmartBoard changes only become scheduled when the secure backend confirms the schedule.
Choose an existing content item, channel and future time. Journey AI checks account readiness and approval requirements before sending the schedule to the backend.
Journey AI combines CreateJourney activity, measured campaign results and authorized connected-account data when available. It shows what is known, what is directional and where more data is still needed.
Board comparisons use only the analytics currently available to CreateJourney.
A small set of useful observations instead of a wall of charts.
Measured campaign outcomes are shown with their evidence source and without turning correlation into proof.
Journey AI receives the current intelligence snapshot, attribution records and advisor context.
Tracked impressions, choices and destination opens by Journey action.
Anonymous first/returning activity and optional-prompt response patterns.
Actual CreateJourney customer events recorded in this browser/workspace snapshot.
Attempted and confirmed outcomes remain separate.
Journey AI connects campaigns and customer actions where evidence exists. It deliberately distinguishes an observed association from a likely relationship and from true deterministic attribution.
Measured campaigns become attribution records. Local before/after changes remain directional unless a backend provides traceable event-level linkage.
Conversion here means recorded CreateJourney actions divided by taps. It is not a payment or revenue conversion unless those systems are connected and measured.
A metric or change recorded directly by CreateJourney or an authorized provider.
Timing and measured movement support a relationship, but other factors could have contributed.
Only used when event-level tracking can connect the source action to the outcome. Local before/after comparisons never receive this label.
Journey AI will list the important data gaps here instead of filling them with assumptions.
Journey AI looks forward only as far as the evidence allows. Forecasts show confidence, sample size and assumptions. When there is not enough history, the advisor says so and recommends a test rather than pretending to know.
Journey AI is evaluating available history, measured campaigns and board performance.
Forecasts are generated only when a minimum evidence threshold is met.
Cross-board differences and measured negative outcomes appear here. They are not automatically treated as future trends.
Recommendations combine business type, owner preferences, measured learnings and current operational signals.
Generate a concise owner-level explanation of what changed, what is uncertain and what Journey AI recommends doing next.
Automations can monitor, prepare, measure and repeat useful work. External or consequential actions remain controlled by role permissions, explicit approval policies, connected-account scopes and secure backend confirmation.
Drafts do not run. An automation is only marked Active after the secure backend confirms activation.
Journey AI applies the safest required policy even if a workflow requests broader autonomy.
Journey AI observes a condition and tells the team. No business change is executed.
Journey AI creates the report, draft, campaign or proposed change, then waits for an authorized person.
Only explicitly authorized low-risk tasks such as measurement, internal summaries, monitoring and draft preparation may run without per-run approval.
Publishing, sending customer messages, changing SmartBoards, changing websites, account/permission changes, payments and other consequential external actions remain approval controlled.
Run history distinguishes previews from backend-confirmed executions.
The recommendation changes with business type, measured history and current evidence.
Describe the trigger, condition and outcome in plain language. Journey AI turns it into a controlled workflow and checks whether the requested approval level is safe before activation.
Example: Every Wednesday, check whether weekend bookings look weak. If they do, prepare an Instagram post and SmartBoard promotion for approval.
The preview shows the effective approval level and whether the requested actions include consequential work.
Fill in the workflow and choose Preview safety plan.
Use business-specific automation packs as a starting point. Packs become editable workflow drafts first; nothing becomes active simply because a template was selected.
Journey AI adapts these packs to the current business profile and available connected accounts.
Signals are observations and recommendations. They do not automatically execute changes.
Preview runs are clearly labeled Preview. Backend-confirmed execution records are labeled Confirmed.
Employees cannot activate automations. Managers can manage normal approval-gated workflows. Owner approval is required for pre-approved autonomy.
Provider actions require the correct connected account and authorized action scope at execution time.
Slow-period and performance conditions use measured evidence thresholds and do not invent missing business data.
If the backend, permission or provider is unavailable, the workflow is not marked executed or active.
CreateJourney uses one SmartBoard hardware family and software entitlements control advanced capabilities. Billing status, prices, invoices and subscription changes are authoritative only when confirmed by the secure billing backend.
Plan capabilities are shown immediately. Prices and checkout terms are loaded from the secure billing backend rather than hard-coded into the browser.
Only the Owner can start checkout, open the billing portal, change subscription level or manage payment details.
Invoices appear only when returned by the secure billing backend.
Every premium capability checks the workspace entitlement model. The browser may show a conservative fallback for UI preview, but server-authoritative actions must re-check the entitlement on the backend before execution.
See what this workspace can currently use and which capabilities require a higher plan.
Can manage billing and plan changes. Feature use still depends on the workspace entitlement.
Can use entitled business tools within Manager permissions, but cannot change the subscription or payment method.
Can only use entitled capabilities allowed by the Employee role and board assignment. Billing remains hidden from execution controls.
Publishing, automation, premium AI and other backend actions must verify both role permission and entitlement server-side.
The plan names and feature groupings below are product defaults. Commercial prices and final billing terms come from the billing backend.
Journey AI tracks workspace usage so owners can understand what is consuming premium capacity. Usage meters are informational until the billing backend confirms the current allowance and period.
Board count is calculated locally; premium AI, creative and automation usage are authoritative only when returned by the backend.
Advanced Journey AI capabilities are gated by workspace entitlements and safe usage limits.
Journey AI can warn the Owner as usage approaches a confirmed limit. It never silently upgrades the plan or purchases additional capacity.
CreateJourney keeps one physical SmartBoard product family. Software plan and workspace entitlements determine digital capabilities; the frontend does not invent hardware charges or recurring board fees.
This command center separates browser checks from server-confirmed production checks. CreateJourney never marks persistence, RLS, backups, Edge Functions, billing, OAuth, scheduling or external execution healthy unless the relevant backend confirms it.
Run the readiness checks to see what is confirmed, what passes locally and what still needs backend verification.
Checks authentication, workspace context and server-reported production services without exposing secret credentials.
Local persistence is inspected directly. Cross-device persistence and database durability require backend confirmation.
Useful browser-level diagnostics for the current build and device.
Export a sanitized diagnostic snapshot for debugging. Secrets, provider tokens, payment credentials and permanent API keys are excluded.
Security status is evidence-based. The browser can inspect its own storage and role state, but database RLS, backup policy, secret management and server audit guarantees remain unverified until reported by the secure production backend.
Production controls are shown as Confirmed, Local pass, Unverified or Blocked.
Backups and restore capability are not inferred from browser state. They require server-side confirmation.
Local audit events are visible here. A production-grade immutable/server audit trail must be backend confirmed.
Scans browser-persisted CreateJourney state for suspicious credential-key names without displaying stored values.
The release gate combines browser-level checks with server-authoritative production checks. Passing local QA alone is never presented as a complete production approval.
Run the full QA suite before treating this build as ready for production deployment.
Checks DOM integrity, accessibility basics, analytics shape, mobile viewport, storage size and runtime health.
Automated browser checks catch common issues but do not replace keyboard, screen-reader and real-device testing.
Runtime measurements are device-specific and informational. They are not a substitute for production performance monitoring.
Critical launch requirements remain blocked until server-confirmed controls are healthy.
This checklist combines current frontend state with backend-confirmed status where available. Unverified backend services remain clearly marked.
Go-live status is evidence-based. CreateJourney distinguishes local readiness from production service verification, and operational controls such as Maintenance Mode require Super Admin authorization plus secure backend confirmation.
Refresh launch operations to check the production services that are available to the secure operations backend.
Service state is not inferred from browser UI behavior.
Maintenance Mode is a server-side operational control. The browser never claims it changed unless the backend confirms the update.
Maintenance state has not been confirmed by the operations backend.
Release metadata is supplied by the production operations backend when available.
A service can be Ready only when the operations backend confirms it.
Track pilot workspaces, SmartBoard activation, Journey setup, Journey AI onboarding, connected accounts and billing readiness. Workspace progress shown here comes from the operations backend; the UI does not invent customer completion data.
Journey AI highlights only backend-supported onboarding gaps and does not guess customer intent.
Owner account and workspace must exist and be accessible.
At least one board must be claimed and active for a board-based pilot.
The active board should have a customer Journey and valid destinations.
AI onboarding and provider connections are required only when the pilot scope depends on them.
Monitor production services, customer-facing failures, incidents and controlled feature rollouts. Incident state and feature flags are server-authoritative; edits require Super Admin access and backend confirmation.
Refresh operations to load incidents, monitoring and feature rollout state.
Includes authentication, public Journeys, board activation, Journey AI, integrations, automation and billing where the backend reports them.
Incidents use stable customer-safe support codes when supplied by the backend.
Feature flags support staged release to internal, pilot or production audiences. A toggle changes only after the backend confirms it.
Generate a sanitized browser diagnostic code for a support conversation. It does not include passwords, provider tokens, payment credentials or permanent API secrets.
Journey AI prepares supported workspace changes first. Nothing is applied until you review and approve it.
Keep campaigns, board redesigns and operating projects together instead of mixing every AI task into one stream.
Manage every physical CreateJourney board, its Journey, assignment and status.
Manage this board, its Journey, assignment and destinations.
Choose up to 3 actions, then use the arrows to control their order.
Update where each action sends the customer.
Copy this board's Journey and destinations to another existing SmartBoard. The target keeps its own permanent identity, name and assignment.
Preview of the customer tap experience.
Claim and configure another official CreateJourney board.
Control who can see and manage each board.
Your current workspace role does not have permission to use this feature.
Your identity, workspace access, security and cloud connection in one place.
Internal board inventory, activation and support controls.
Build 31 · Owner, MiniBoard, customer and production integration system
Build 33 · Production cutover, real integrations and release readiness
Build 32 · Separate test/demo data from real customer data before launch.
Build 33 · Real provider authorization, verified connection state, and provider-confirmed completion rules.
One Journey AI experience, backed by specialist agents that collaborate only when the problem benefits from it.
Simple questions use the fast path. Business-growth, sales, research, revenue and multi-step problems are delegated to the right specialist council. Difficult requests can expand beyond four agents when the extra perspective is likely to improve the answer, while specialists remain parallelized for speed.
Each agent has a defined job, learning focus and evidence boundary.
The Orchestrator scores specialists against the owner’s request. It selects a small council first and expands only for difficult cross-functional work.
Measures routing frequency, successful participation and latency now. Revenue/outcome scoring activates only when CreateJourney has provider-confirmed evidence.
Plan with Journey AI. Create with specialist agents. Schedule, publish and confirm through the connected social execution layer.
CreateJourney keeps the strategy, customer intelligence, approvals and attribution. The publishing gateway handles channel-specific validation, scheduling, media delivery and provider confirmation.
Your complete Journey AI work history, active projects and results.
See everything CreateJourney can do for your business.
Every feature below hands the goal directly to Journey AI. You choose from clear options, approve the direction, and Journey AI carries the work forward. Every project is automatically saved in Journeys.