Inbound
PSTN/SIP or Digital entry resolves tenant, purpose and applicable policy before Human, AI or system participation.
Global communications
Global communication should flex around people —
not force people around infrastructure.
Jodoworld is designed to bring Digital, telecom, Humans, AI, carriers, numbers, languages, time and policy into one governed business model. Exact support is frozen by Release Profile rather than assumed globally.
Digital + C3
One business journey across communication environments.
Inbound and outbound are communication directions within one governed model. Digital and telecom can continue into one another where country, policy, consent, entitlement, provider and deployment rules permit.
Outbound
A Human, workflow or AI begins from the business journey, then uses an approved alias, presentation identity and eligible route.
Continuation
A permitted Digital↔C3 move should preserve business/process state, authorised participant context, language and evidence correlation.
Recovery
A provider or media failure does not have to become a terminal business outcome while a valid permitted continuation remains.
Business identity without exposing the person
Separate who someone is from how they can be reached.
Approved Product contracts separate participant identity, acting capacity, communication alias, presentation identity and the actual endpoint.
WHOParticipant
The governed Human, team, partner, AI or system identity.
CAPACITYActing role
The organisation, role and authority under which the participant acts.
BUSINESS IDENTITYCommunication Alias
A stable business-facing identity where offered.
NETWORK IDENTITYPresentation Identity
The permitted number or network-facing identity for a communication leg.
REACHABILITYEndpoint
Browser, app, SIP/desk phone, corporate/mobile number or approved partner endpoint.
Global means context-aware
Country, carrier and time are policy — not afterthoughts.
Country Capability Profile
Product-visible eligibility can vary by country/region for Digital, telecom, AI, RTLT, recording, numbers and providers.
Multiple carrier routes
Approved carrier configurations can coexist where offered; policy and required capability come before cost optimisation.
Temporal policy
Local time, team hours, holidays, DST and regulated contact windows can govern whether the next step is allowed.
Alternatives instead of dead ends
Where permitted, policy can offer AI continuation, callback, next window, BPO/partner, another geography, alternate channel or a truthful unavailable state.
Waiting is part of the business journey
Waiting, callback, overflow, cancellation and unavailable states preserve the business objective and permitted alternatives.
Human RTLT
Real-time language translation can assist a Human-owned conversation where implemented and validated, while original/translated evidence remains distinguishable.
Release Profiles
Global capability is explicit — not implied.
A Release Profile freezes the exact scope that may be represented as supported.
A Release Profile can identify
country / regiondeploymentcarriers / providersnumber / presentation scopeinbound / outbound / Digital↔C3 scopelanguages / RTLT pairsuse-case profilesentitlementcompliance / recording policybuild / environmentvalidation / Product acceptance