Send an open call to your team
Let an available internal notary accept the session instead of selecting a specific person.
Choose a pool, not a person
A team open call lets eligible members of your internal pool accept the session. This is different from direct assignment using a specific notary email.
| Workflow | Request | Account setup |
|---|---|---|
| Named teammate | Include session_notary_email | Linked and eligible notary. |
| Any teammate | Omit session_notary_email | Internal-team pool routing. |
| BlueNotary network | Omit session_notary_email | Network pool routing. |
Configure your account
Confirm internal-team routing, eligible members, open-call permissions, and the intended creation or participant-driven dispatch trigger. If you need network fallback, verify that policy explicitly.
Do not add an invented internal_notary or fallback_to_network field to the session request. The current public request does not expose those switches.
Create without a named notary
The payload can look the same as a network request. Your account configuration distinguishes the pool.
{
"notarization_id": "team-order-1042",
"signing_type": "ron",
"session_type": "gnw",
"notarization_timing_type": "notarize_now",
"all_signers": [
{
"first_name": "Sam",
"last_name": "Signer",
"email": "sam@example.com"
}
]
}Schedule a team open call
Use notarize_later with session_timing when the session has an appointment. Confirm strict-schedule behavior and notification lead time with the configured team workflow.
- Verify the displayed local appointment time.
- Observe dispatch timing during testing.
- Agree on the escalation path if no team member accepts.
Monitor acceptance
Store the created session ID and observe open_call_accepted. Session creation does not guarantee a notification was dispatched or that a notary is available.
- Created
Your order has a BlueNotary session.
- Dispatched
The configured workflow has attempted to notify eligible members.
- Accepted
A notary accepts the call; participant flow can continue.
Handle no response
Use the agreed account escalation/fallback policy and show a clear waiting state to the signer. Do not manufacture a second session to represent an unaccepted first one. Keep cancellation and support reconciliation tied to the original session ID.