JobFlow Help & Setup Center
Get oriented. Build the right setup. Know where to look.
Personal assistants and Business operators have different onboarding, workspaces, controls, and goals. Start in the product lane you actually use.
⌕Search becomes active with the customer portal.
Choose your product lane
Two products. Two different ways to get started.
P
Individuals
BPersonal assistant onboarding
See how your assistant starts small, develops an approved working style, keeps only the context you choose, and grows into your routines and projects.
Open Personal onboarding →Businesses
Business operator onboarding
Choose managed implementation with a quoted setup fee or free guided self-setup with training, templates, and validation.
Open Business onboarding →Browse help
Answers organized around what you are trying to do.
Using your workspace
Approvals and actions
Memory and preferences
Plans, billing, and upgrades
Troubleshooting
The four states that matter
Know what happened—and what did not.
DraftThe assistant prepared a proposal.
→ReviewA person checks the exact action.
→ApprovePermission applies to that version.
→CompleteA connected system confirms the result.
A draft is not represented as an email, message, booking, quote, payment, or record change unless the approved connection actually completed it.
Professional operating reference
Workspace, activity, connections, and support.
Workspace and account isolation
Each customer is designed to have a separate authenticated workspace. Personal and Business lanes remain separate; membership and workspace scope determine what account data can be returned.
Memory and context
Approved preferences, routines, and operating context should be reviewable. Public-site browsing is not a customer memory source, and a customer can correct or retire stale context.
Connection states
Connections use visible states: Not connected, Pending approval, Sandbox, Connected, or Revoked. Each provider requires customer-specific authorization, configured scope, and a revoke path.
Plans and billing
The account should show the active entitlement and hosted billing access once production billing is configured. Card details are handled by the approved hosted payment provider—not by a JobFlow webpage.
When something looks stuck
Check whether the item is waiting for owner approval, missing required information, blocked by a disconnected provider, or outside the configured workflow. The activity trail should show the exact state rather than a vague failure.
Approved continuity
Memory that earns its place.
JobFlow is designed to become more useful because you choose what it keeps—not because it silently collects everything.
Keep the useful context
Save the preferences, rules, routines, project decisions, brand voice, and repeatable process you want the workspace to use again.
Correct it in plain language
Review what matters, fix an outdated assumption, or remove context you no longer want. An approved correction can improve future drafts and help avoid the same correction again.
Stay in control
Public browsing, a sample preview, and unapproved material are not treated as customer memory. Personal and Business context stay in their chosen lane.
Connection possibilities
A connection catalog built around your real work.
Choose only the tools that make a workflow better. JobFlow can prepare work for your review, organize approved information, and support the communication rhythm you choose.
Email, Slack, Discord, Telegram, WhatsApp
Prepare replies, owner updates, community summaries, moderation queues, and follow-up drafts. Each channel is separately selected, permissioned, configured, and tested.
Calendar and scheduling
Turn requests into proposed times, protect important commitments, and bring booking decisions to the owner before anything is confirmed.
Google Drive and approved files
Organize source material, prepare briefs, compare documents, and make a reusable reference library for the work you approve.
Intake, CRM, forms, and reporting
Map the chosen workflow from inquiry to owner decision. A business connection is designed around its exact permissions, records, and escalation rules.
No connection is on by default
Connection is a decision—not a checkbox.
Every provider starts unconnected. You choose the purpose, scope, permissions, approval rule, and revoke path before it moves through Not connected → Pending approval → Sandbox → Connected. You can revoke it when the workflow changes.
What a good connection looks like
Useful enough to save time. Controlled enough to trust.
ChooseName the outcome and information it needs.
→ScopeSet permissions, limits, and owner controls.
→TestUse a sandbox before real work.
→ReviewKeep activity and revoke controls visible.
Bring the exact workspace, workflow, and outcome.
Tell us whether you use Personal or Business, which plan or preview you are viewing, what you expected, and the last visible status. Do not send passwords, access codes, payment-card information, or provider credentials.
Contact JobFlow