Frequently asked questions

Not at call time. Schedule to Call Me rings your verified ordinary phone. You answer that call before the recipient is connected.

No. The callback reaches your ordinary phone service. The platform operates the bridge between the two phone legs.

The recipient sees the selected approved displayed caller ID. Your private callback phone is not used as an automatic fallback.

The callback phone is where we reach you first. The displayed caller ID is the separately approved number shown to the recipient.

No. The service calls you first and does not intentionally call the recipient until your call reaches the documented connect step.

The product never silently substitutes a private callback number. Fix or select an approved caller ID and try again.

The provider may have accepted the request, but the platform cannot yet prove the outcome. Wait for reconciliation and do not submit a blind duplicate.

Exactly one standalone phone number. Do not include a second number, extension, or contact block.

Yes. A national number uses the country of your selected verified callback phone. A number in another country must begin with + and its country code.

Yes. Common punctuation, Unicode dashes, and non-breaking spaces are accepted before country-aware validation.

You receive a confirmation or problem email and can check Calendar activity. Silence is never confirmation.

Yes. Make an actual event-content or start-time change and send the update. Changed same-sequence Google events are retained safely.

An otherwise valid Calendar request is scheduled with recording Off. The confirmation and Calendar activity explain the fallback.

Yes, when the required entitlement, workspace policy, and permissions are active. Silent recording additionally requires the typed attestation.

Regular recording plays the required announcement only to the answered recipient and begins recording after the destination answers.

Silent recording has no announcement or beep. You are responsible for lawful use and any required consent.

A saved workspace policy and current entitlement are separate. The policy can remain saved after a trial or add-on expires.

Recording media is handled asynchronously. Playback and download appear only after the private copy is ready and authorized.

Every portal page shows a trial banner with active, expired, or canceled status, exact end time, days remaining, and the temporary feature list.

Web, Calendar, SMS, Direct PIN, Phone Snooze, Regular Recording, and Silent Recording. Dial Now, API/MCP, and extra caller IDs are not included.

No. Access time and wallet credit are separate. A Super Admin trial extension changes access dates only.

It is the published $0 monthly membership with Web and Calendar included, no monthly usage credit, and optional paid add-ons. Usage still requires available wallet funds.

Only after the provider confirms the billing action and the platform stores the corresponding entitlement. A redirect or checkout page alone is not activation.

When enabled with a valid reusable payment method, it adds the configured amount below the configured threshold, subject to daily and monthly limits.

It covers eligible SMS scheduling and Direct PIN calling. Phone Snooze is a separate entitlement even when sold alongside it.

No. Create a new PIN if you no longer know it. Keep it private and never put it in support notes.

No. A verified callback phone belongs to one human user, though that user may use it across their own memberships.

No. Customer organization roles and platform roles are separate security boundaries.

No. The product focuses on callback scheduling, connection, identity, history, and team controls. Eligible API, MCP, and webhook features support integrations.

Authorized first-party Call detail may show that call’s destination. Lists, integrations, exports, callback phones, caller IDs, and provider-leg views remain masked.