Platform
Core platform changes
Document shared identity, permissions, workflows, data, billing, and platform behavior.
Release notes
Track what changes across MobDial products and platform surfaces.
Use the release-notes hub to understand product changes, API and workflow implications, operational impact, rollout boundaries, and follow-up documentation without mixing changelog entries with unsupported production claims.
One MobDial identityRole-aware workspacesAPIs + automation
MobDial operating system
Product workspace preview
Customer
Resolved
Workflow
Running
Outcome
Tracked
Live workflow
EngageVoice, message, agent, or digital event begins
OperateCustomer context and business state stay connected
ImproveAutomation and analytics use the same resource trail
Execution guardrails
- One customer identity
- One conversation model
- One permission layer
- One audit trail
Product
Follow customer-facing capabilities and workspace changes
Developer
Track APIs, events, webhooks, SDK-facing contracts, and migration notes
Operations
Call out rollout, configuration, provider, and support implications
Trust
Separate implemented changes from verified deployment and release evidence
Change communication
Release notes should explain impact, not just list commits.
A useful release entry identifies the affected product, audience, compatibility impact, rollout state, migration needs, and where to verify the current behavior.
Communications
Voice and messaging changes
Call out routing, provider, number, queue, campaign, and conversation-impacting releases.
AI
Agent and model changes
Explain changes to agent behavior, tools, knowledge, speech, evaluation, and handoff surfaces.
Developer
API and webhook changes
Describe contract, event, authentication, SDK, and migration implications for builders.
Security
Security and trust updates
Publish customer-relevant control or policy changes without turning internal work into unsupported certification claims.
Operations
Rollout and verification
State when a change is available, where it is enabled, and what evidence confirms the intended environment.
Release discipline
Describe the change. Explain the impact. Point to verification.
Scope the release
Identify the product, routes, roles, APIs, providers, or workflows affected.
Explain compatibility and rollout
Call out migrations, flags, defaults, limitations, and environment-specific behavior.
Link to evidence and next steps
Direct readers to documentation, tests, status, migration guidance, or support as appropriate.
Next step
Keep product changes understandable from build to operation.
Use MobDial documentation and status surfaces alongside release notes when a change affects implementation or production operations.