Your phone connection
Connection improvements are applied automatically. Your team can keep using the existing connection. Any required setup changes are explained in the release notes.
Keep your team up to date.
See what’s new, what updates automatically, and when your administrator needs to take action.
First managed package build: namespace dealmachine, packaged connector app
Released 2026-10-29
- Shipped as the managed package "Caller Intelligence" (namespace dealmachine) built from this source; the source kit remains available for administrators who prefer it.
- Includes the packaged DealMachine Caller Connector app so administrators can authorize the phone connection without DealMachine staff.
- Named-credential callouts, custom-permission checks, the caller platform event channel and record field names now resolve the package namespace at runtime, so the same code runs from the source kit and from the managed package.
- Settings sends the package namespace to the DealMachine connector, which uses it for the Apex REST ingress path and the registration check.
- Apex tests no longer depend on permission sets already assigned in the org; they pass in a fresh packaging build org.
- Permission-set queries in team routing run in user mode; expected-failure tests assert explicitly.
- Connector: static files no longer answer with a wildcard CORS header.
What updates automatically?
Your Salesforce app
Your administrator installs each new version from the package link; it upgrades in place and keeps your settings, connection and routing. The app checks for new releases and shows a notice when one is available.
Install or upgrade to v0.8.0 ↗How the app checks for updates
Starting with version 0.4.0, Caller Intelligence checks the published release automatically, at most once per day in each administrator’s browser while the app is open. It also checks on the next opening when the previous check is more than a day old.
If a newer version is available, administrators see a quiet notice. In Settings → App updates, they can see their installed version, the latest published version, the last successful check, and select Check now.
Checks read public version information. They do not send caller records or account credentials, open over a call, or install an update. A failed check does not affect incoming calls or texts.
Customers on older versions need one administrator-assisted update to receive this checker. It cannot add itself to an older installation.
Get help updating the Salesforce app.
- Open Settings → App updates and note your installed version. If App updates is missing, your installation predates the checker.
- Have your Salesforce administrator open the package link above, sign in to a sandbox first if you have one, and install the new version over the existing one.
- Install it in production the same way, then test an incoming call and text before your team relies on it.
Opens an email draft for you to review and send. Include the installed version; keep passwords and API keys out of email.
Will Salesforce updates install themselves?
Not yet. Automatic checks notify you of releases; your administrator installs them from the package link, which takes a couple of minutes and keeps every setting.
Salesforce can push upgrades to every subscriber automatically once the package has completed the AppExchange security review and push upgrades are enabled for it. That is in progress; until then the install link is the upgrade path.
Technical update resources
Optional source kit for administrators who deployed from source instead of the managed package. Validate in a test org, review local customizations and new permissions, and verify calls and texts afterward.