Plain answers before you apply.

Yes, for approved early-access workspaces. CaptureBeacon now has an isolated invite-only production service for real work. Access remains reviewed and gradual while the product, support process, and pricing mature.

Solo service providers, new businesses, event teams, established organizations, and nonprofit programs can apply. You do not need a registered company or professional license.

CaptureBeacon supports a shared operating path for appointment-based services, mobile jobs, events, and organizational programs: request, schedule, assign, work, document, complete, and follow up. Approved workspaces can add specialty tools when their work needs them.

It turns scattered requests, calendar details, customer information, team assignments, field updates, and follow-up into one repeatable operating routine. That structure can help an owner serve more customers and add team members without relying on memory or rebuilding the process for every job.

Sign in with Microsoft to submit a brief workspace application and check its status. We review it and email you when a decision is recorded. Approved applicants choose a plan, pay through secure checkout, and finish creating their workspace. Applying creates no charge. We do not promise a response timeframe.

For now, Microsoft provides the secure sign-in used by CaptureBeacon. Microsoft handles your password; CaptureBeacon never receives it. Google sign-in and passwordless email links are reasonable future options, but they are not active today.

No. The application site never creates a workspace on its own, and applying does not promise acceptance, pricing, or an activation date.

Yes. Essential is $5/month and Plus is $15/month total, including Essential, plus applicable tax. Approved applicants can pay through secure checkout before creating their workspace. Application and review are free. Existing workspaces also require a paid subscription.

Yes. Cancel before renewal to stop the next charge. Service continues through the end of the period you already paid for. Unused time is not refunded, except where required by law or when a duplicate charge, billing mistake, or confirmed service failure is corrected.

Manager is for planning, assignments, oversight, delivery, and closeout. Field is the focused mobile experience for the current job or event: brief, checklist, timing, assigned stations or service tasks, status, and help.

The owner invites the exact email account and assigns its role. CaptureBeacon then gives that person resumable onboarding, explains the responsibilities and privacy expectations for that role, and directs them to the correct workspace tools without revealing unrelated customers or manager controls.

Yes. Field and mobile jobs are designed for phones and tablets. A team member can see assigned work, use an arrival window and directions, tap status updates, complete a checklist, request manager help, and prepare a customer summary. Manager also has compact, workspace-aware phone navigation while retaining its fuller desktop layout.

In approved alpha tests, yes. A visit can have a shared crew, one designated site lead for final sign-off, and a checklist history that shows authorized managers or leads who completed each action.

Controlled appointment and portrait scheduling is available only in approved tests while the broader service path is reverified. The intended workflow lets a provider define working days, hours, breaks, service duration, spacing, and timezone so customers see only openings that fit.

Yes. Approved workspaces can schedule recurring service. Plus workspaces can use manager-reviewed route and call-out coverage proposals with owner consent and monthly limits. AI assistance is active for eligible Plus workspaces. Route planning remains early access while complete real-customer routes are verified, and CaptureBeacon never silently moves a customer appointment.

Yes. Approved workspaces can use a private live walk-in board for unscheduled arrivals. The board stays inside the workspace rather than publishing the customer list.

Yes. The invite-only production service is configured for transactional messages such as confirmations, completion notices, and private feedback links. Recurring marketing messages are not silently enabled.

Not yet. Consent, stop handling, and delivery safeguards are prepared, but no texting provider or paid SMS service is active.

Not as an active production offering. Calendar export and synchronization remain useful, but approval responses are being redesigned inside the consolidated CaptureBeacon workflow.

CaptureBeacon workspace subscriptions are paid through secure Stripe checkout. Customer deposits and payments for a provider’s own services are separate from CB subscription billing. CB does not collect those service payments through its subscription checkout.

Preloaded field work is designed to queue eligible updates and synchronize them in order when service returns. Offline and multi-device behavior remains part of controlled alpha verification.

No. Field access is tied to the exact assigned work and role. Workspace-wide management information is not part of that view.

No. Participant-facing pages expose only the specifically approved public information and actions for that event.

Yes. An approved workspace can download one permanent customer-access sign plus event and Photo Hub signs. The permanent sign follows future service and scheduling updates, while event signs lead to that event’s approved registration, queue, appointment, or gallery actions. The signs do not contain participant information.

Yes. A manager can switch the current device into the participant event screen and set a temporary return PIN. The participant does not receive Manager controls, and repeated incorrect PIN attempts trigger a short lockout.

Camera synchronization appears beside the other Field readiness items. After the clocks are synchronized—or an offset is recorded—the assigned person marks that item complete, and CaptureBeacon keeps the same event-scoped completion history used by the rest of the checklist.

No. CaptureBeacon tracks operational milestones, approved links, counts, dates, permissions, and history. In the mobile-job test, selected photos stay on the field person’s device until they deliberately share them through an outside message or email app. Photograph files and galleries remain in the chosen outside service.

Not silently. Every planned checklist item must be resolved as completed, deferred, or unable to complete. Deferred or incomplete work can require a reason and manager review, while private company notes remain separate from the customer-facing completion summary.

Yes. The completion message can ask the customer to confirm the work, report something missing, or request additional support. The response is private operational feedback tied to that job—not a public review.

The workflow can track an approved external destination such as Pixieset, Dropbox, or another selected provider. Gallery publication remains unavailable until photography is marked complete, preventing an unfinished event from being released accidentally. Broader integrations still vary during early access.

Closing operations stops live event work without immediately removing the public participant page. Gallery-interest requests can remain available during the delivery period. Archiving the event closes that intake and preserves the completed history.

Yes, when the group is excluded from the community gallery. A manager saves a secure external delivery link, sends it through the configured email service, and CaptureBeacon records who confirmed the delivery and when. This is limited to portrait work; CaptureBeacon still does not store the photograph files.

The same path can support a small portrait session or a larger staffed event: plan, assign, work, hand off, approve, deliver, and close. The details and team size change, but the operating rhythm does not.

Support diagnostics are controlled and owner-approved. Support should not receive broad, permanent access to a private workspace simply because a problem is reported.

CaptureBeacon is currently a program of Frames of Service Foundation. Its credentials, data boundaries, and operating records are kept structured so the product can remain distinct if its ownership or organizational home changes later.