The Solution Workshop guide

Connect deliberately.

Keep ownership of your business tools. Authorize a specific connection, verify its outcome and know what happens when it is unavailable.

Capability review: September 17, 2026. Status applies to the specific action described.

Read the status labels

LIVE NOW: The named action is deployed. Read its limits; this label does not apply to every feature beside it.
PILOT: Controlled testing or a prototype. It may use fictional data or need a guided session; it is not a general customer rollout.
REQUIRES CONNECTION: An integration depends on an authorized account, configuration and a verified outcome. An available adapter is not a connected customer account.
PLANNED: A product direction or unfinished capability. No availability date or included service is promised.

Your number and forwarding

PILOT

You may want to keep answering your existing number and forward only missed calls, or use a separate pilot number for selected work. Direct calling and carrier forwarding are separate tests.

First decide the behavior: no answer, busy, all calls or another supported condition. Carrier and line-product rules differ. A forwarding code should match that exact situation, not be guessed from a carrier name.

Agree on the intended receiving number and voice identity.
Test a direct call to the pilot route.
With the owner’s approval, test the selected forwarding behavior on the actual line.
Verify both an answered call and a call that should forward. Keep a supported way to undo the setup.

A purchased voice number is not automatically ready for SMS. Messaging registration, approved sender use, inbound routing and delivery tests are separate. Signup does not automatically buy numbers or enroll a customer in a campaign.

Your calendar and email account

REQUIRES CONNECTION

A calendar is the source of scheduling truth; the mail or calendar app on a device is only one way to view it. For example, Outlook can display a Google-hosted calendar. The connection must target the actual provider and the calendar the owner authorizes.

Calendar adapters exist for authorized use, but self-service tenant calendar onboarding is not implemented. Voice booking tools are also still planned. An empty response from one calendar is not proof that the intended calendar is accessible or that a time is safe to offer.

A useful first check is read-only. Identify the calendar and time zone, then verify an existing known busy interval and a known open interval. Do not create an appointment just to prove that credentials work.

Free/busy access answers when a calendar is occupied without needing event titles. Creating an event or inviting a guest is a separate write action with separate authorization and a result to verify.

Email should also be connected by its owner through an approved supported path. The product does not offer a general self-service email connection or standalone transactional-email workflow today. An email draft is not a sent message; a calendar invitation must be checked independently.

Personal channels and work updates

PLANNED

The Premium direction includes personal-channel integrations on iPhone or Android only where a supported connector and explicit authorization make the workflow possible. BlueBubbles and Android integrations are not live, and private iMessage access is not promised.

Slack is used for an internal private-owner notification pilot, not a required customer download. A future customer notification channel needs its own consent, destination, delivery verification and handling for changed or reassigned numbers.

Traccar is separate optional phone tracking. The dashboard work is built around recorded consent and on-shift visibility. Device installation alone does not prove that a current position reached the right tenant dashboard; inspect shift state, last update and connection status.

Payment connections

PLANNED

The intended job-payment connection belongs to the Pro through Stripe Connect. It is separate from the Pro’s subscription with Solution Workshop. Neither tenant Connect money movement nor active subscription billing is implemented.

The existing single-account sandbox POC is useful for learning about Checkout and signed payment updates. It is not proof of connected-account onboarding, live charges, payouts, refunds or disputes for a tenant.

Read the two payment flows

What moves a connection forward

We describe the roadmap by the evidence needed to move forward, without promising dates.

Calendar-backed voice booking
Prove the intended calendar, then bounded slot offers, explicit selection, conflict rechecks and one retained booking reference. Verify messages separately.
Tenant phone onboarding
Bind an approved number to the correct business. Verify voice, messaging and forwarding independently before inviting customer traffic.
Job payments and subscriptions
Prove test-mode account scoping, payment-state handling and retries, then resolve live-use approval and operational responsibilities.
Historical account access
Use stable customer identities and independent authorization. Pass wrong-person, reassigned-number and cross-tenant tests before connecting old records to conversation.
Additional connectors
Define the smallest useful permission, data boundary and expected result. Custom work requires a scoped agreement; an integration name alone is not a delivery promise.

Ask these before connecting

What exactly am I authorizing?

Name the account, data and action. Reading free/busy data, writing an appointment, sending a message and charging a customer are different permissions. Credentials should stay on the server; do not paste them into a public demo.

How do we know it worked?

Keep the provider’s response and inspect the resulting state. Confirm the recipient where relevant. “Connected” is not enough if the workflow still cannot reach the correct calendar, customer or account.

What if I disconnect it?

Before adopting a connection, agree on revocation, outstanding work and data retention. Removing access must prevent new actions; it does not automatically remove every previously stored record. Ask what is retained and who can still see it.