Quick Answer: Aircall is completing the final step of an infrastructure upgrade to its Salesforce integration during a maintenance window on Saturday, September 5, 2026, 02:00–04:00 UTC (Friday, September 4, 9:00–11:00 PM Central Time). Aircall expects the actual interruption to last 20–30 minutes — the two-hour window is a safety buffer. During that gap only, presence status sync (Omni-Channel) and click-to-dial record linking (Salesforce CTI) may be affected. Call logging, tasks, AI insights, sentiment analysis, and SMS are not affected. No action is required: no backfill, no reconnection, no settings changes. The integration resumes automatically after the cutover.
What changed
Aircall has notified customers of a scheduled maintenance window covering the final step of an infrastructure upgrade to the Aircall–Salesforce Integration. According to Aircall's scheduled-maintenance customer notice (September 3, 2026), the work is a backend routing change with a brief cutover gap — the kind of change that completes a migration already underway behind the scenes.
Two things in the notice are worth underlining:
- The window is a buffer, not the outage. Aircall expects the interruption to last 20–30 minutes, not the full two hours. The longer window is standard safety margin in case the cutover runs long or needs a retry.
- Most of the integration is already migrated. Call logging, tasks, AI insights, sentiment analysis, and SMS already run on the upgraded infrastructure on a separate pipeline that this change does not touch. This final step moves the remaining pieces.
Who's affected
Only Aircall customers using the Salesforce integration, and only for two specific behaviors during the cutover gap:
- Presence status sync (Omni-Channel users). An availability status change made during the gap may be delayed or may not go through.
- Click-to-dial record linking (Salesforce CTI users). A call initiated via click-to-dial on a Salesforce record during the gap may not link to the correct Salesforce record. Note the nuance: the call still happens and it still logs — it is the record association that may be wrong.
Everyone else — including Salesforce users who don't use Aircall, and Aircall users who don't use the Salesforce integration — sees nothing. And per Aircall's notice, call logging, tasks, AI insights, sentiment analysis, and SMS continue running normally for everyone, even during the gap.
What to do (spoiler: communicate, don't configure)
Per Aircall's notice, no customer action is required. This is a backend routing change: no data backfill, no reconnection, no settings to update. The integration picks up automatically once the cutover completes.
But "nothing technical" doesn't mean "nothing at all." When we advise clients on vendor maintenance windows like this one, the two things worth doing are communication, not configuration:
- Send a one-line heads-up to agents on Friday-night and weekend shifts. Something like: "If you change your availability status or use click-to-dial between 9–11 PM CT Friday and something looks off, wait a few minutes and retry." That's the entire message. It prevents a confused agent from filing a ticket or assuming their phone is broken.
- Run a two-minute smoke test after the window — Monday morning, or Saturday if someone is on. Change a presence status and confirm it syncs. Make one click-to-dial call from a Salesforce record and confirm it logs against the right record. If both pass, you're done.
If you discover that a call made during the gap didn't link to its record: the call still logged (logging is unaffected), so find it in Aircall and associate it to the correct Salesforce record manually after the window.
Timeline
The maintenance window is Saturday, September 5, 2026, 02:00–04:00 UTC, which lands Friday evening across the continental US. Aircall's expectation — attributed as such — is 20–30 minutes of actual interruption inside that two-hour buffer.
| Time zone |
Window start |
Window end |
| Pacific (PT) |
Fri, Sep 4, 7:00 PM |
Fri, Sep 4, 9:00 PM |
| Mountain (MT) |
Fri, Sep 4, 8:00 PM |
Fri, Sep 4, 10:00 PM |
| Central (CT) |
Fri, Sep 4, 9:00 PM |
Fri, Sep 4, 11:00 PM |
| Eastern (ET) |
Fri, Sep 4, 10:00 PM |
Sat, Sep 5, 12:00 AM |
| UTC |
Sat, Sep 5, 02:00 |
Sat, Sep 5, 04:00 |
| Central European (CEST) |
Sat, Sep 5, 4:00 AM |
Sat, Sep 5, 6:00 AM |
| Australian Eastern (AEST) |
Sat, Sep 5, 12:00 PM |
Sat, Sep 5, 2:00 PM |
A note on reading maintenance notices
This one is a good example of the genre, and two patterns are worth recognizing the next time a vendor notice lands in your inbox:
- "Expected impact inside a buffer" is standard practice. When a notice says the window is two hours but the expected impact is 20–30 minutes, the vendor is reserving headroom, not predicting a two-hour outage. Plan around the buffer; expect the smaller number.
- The "what's not affected" list is the part most notices skip. Many vendors tell you what breaks and leave you to guess about everything else. This notice explicitly lists call logging, tasks, AI insights, sentiment analysis, and SMS as unaffected — and explains why (they already run on the upgraded pipeline). That level of specificity is what lets you answer "will X keep working?" without opening a support ticket.
Frequently asked questions
Will calls drop during the maintenance window?
The notice does not say calls drop. It describes a backend routing change with a brief cutover gap, and the only impacts it lists are presence status sync delays and click-to-dial record-linking misses. Calls placed during the gap still log normally.
Will call logging stop?
No. Per Aircall's notice, call logging continues running normally — it already runs on the upgraded infrastructure on a separate pipeline that this change doesn't touch.
Do I need to reconnect the integration or change any settings?
No. Aircall's notice is explicit: no data backfill, no reconnection, and no settings updates. The integration picks up automatically once the cutover completes.
What if a call made during the gap doesn't link to its Salesforce record?
The call still logged — logging is unaffected. After the window, find the call in Aircall and manually associate it to the correct Salesforce record.
Does this affect Aircall's AI features?
No. Per the notice, AI insights and sentiment analysis are unaffected; they run on the upgraded infrastructure on a separate pipeline.
Does this affect the HubSpot integration?
Aircall's notice covers the Salesforce integration only — it says nothing about HubSpot. There is no indication in the notice that any other integration is affected.
What about SMS?
SMS continues running normally, per the notice — same upgraded pipeline as call logging and AI insights.
Sources
- Aircall scheduled-maintenance customer notice, "Scheduled maintenance: Salesforce Integration, Sep 5 (02:00–04:00 UTC)" (received September 3, 2026). All maintenance specifics in this post — the window, the 20–30 minute expected impact, the affected and unaffected features, and the no-action-required guidance — come from this direct customer notice.
- Aircall status page — for live incident and maintenance status around the window.
- Aircall Help Center: How to configure your Salesforce integration — the general integration reference (no maintenance-specific detail is published there; the window specifics come from the customer notice above).
Running Aircall alongside Salesforce and want a second set of eyes on your setup? Vantage Point helps teams get more out of Aircall + Salesforce — implementation, integration configuration, and ongoing admin support. Whether you're planning a rollout, cleaning up call-logging rules, or just want a partner who reads the maintenance notices so you don't have to, talk to our team.