# What happened to Airkit.ai The room usually agrees that a broken Airkit.ai bookmark means the product must be switched off and rebuilt. That agreement is the problem: it fits a shutdown, a price, and a screen, and the announcement of 16 October 2023 supports none of them. **Published:** 2026-05-22 **Canonical:** https://synconai.com/what-happened-to-airkit **Author:** SynconAI Architecture Team ## In short Settle six things before a broken Airkit.ai bookmark becomes a rebuild. Salesforce completed the acquisition on 16 October 2023 and placed the work in Service Cloud. Airkit.ai built customer-service applications. The cited announcement publishes no price and no end date, and it describes no current screen. A menu from a 2023 demo is not a screen to redraw. Build from channels, cases, and a queue. ## Sources - **Salesforce Signs Definitive Agreement to Acquire Airkit.ai** (retrieved 2023-10-16) https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-airkit-ai/ > Salesforce completed its acquisition of Airkit.ai on October 16, 2023. ## What to take away - Decide the ticket is an ownership and date question, closed on 16 October 2023 and placed in Service Cloud, before anyone prices a rebuild. - Name the people who can change the shipping window, the refund rule, and the queue. Salesforce owning the company does not name them. - Leave the price cell blank. A zero, a remembered figure, and a licence fee are three different claims, and the cited announcement supports none of them. - Scope any build as channels, cases, knowledge, and a queue. Do not redraw a menu from a 2023 demo. ## The guide The room usually agrees before anyone has opened a record. A service director has an old bookmark for Airkit.ai. The page that loads no longer matches the login the team remembers. The ticket in front of her already treats that mismatch as three decisions at once: the product is finished, Salesforce owns whatever replaced it, and the team must switch the old thing off this quarter. People nod, because the bookmark is genuinely broken and the ticket is genuinely waiting. That agreement is the problem. A broken bookmark is compatible with a completed acquisition whose work was placed in Service Cloud, with a service application some teams still run, with a demo nobody in the org ever turned on, and with a shutdown date nobody has published. Only the first is a fact the announcement will support. The others are guesses, and a guess is what gets priced. Airkit.ai built customer-service applications. Salesforce completed the acquisition. The announcement placed that work in Service Cloud. Placement is a home. It is not a picture of a screen, and it is not an instruction to rebuild the old application inside a Case because the ticket says migration. Releases have landed since the close. A menu from a demo in 2023 is not a menu to redraw. If the org has a screen, open it. If it does not, the slide stays blank. The completion line is the sentence worth keeping in the brief, unchanged. "Salesforce completed its acquisition of Airkit.ai on October 16, 2023." What follows are the questions that stop the ticket becoming a rebuild. Each has a good answer and a bad answer. The difference is whether the answer names a person, a document, a product, or a year. A DVD, a Reddit thread, a YouTube video, a TikTok, a course, a book, or a certification is not a source for the date, the price, or a shutdown. | Question | Who has to answer it | What a bad answer usually means | | --- | --- | --- | | What problem is the ticket solving | The service director holding the ticket | A bookmark becomes a rebuild nobody can test | | Who owns the company, and who owns the rules | Salesforce for the company; a named person for each rule | The path is expected to arrive already configured | | What does 16 October 2023 decide | Whoever is writing the timeline, from the announcement | The close is reused as a go-live or a sunset | | What may be written about price | Finance, with the announcement and the order form | A blank cell is filled so the slide looks finished | | Is there a shutdown to schedule | The owner of any login that still works | A quarter is chosen because the template has a box | | What would you build | The person who can name a channel and a queue | A 2023 menu is redrawn and priced as a migration | ## What problem is the ticket actually solving? The question is what the director needs decided this week, and which of those needs the announcement can meet. Three needs arrived on one ticket. Who owns the company, and when the purchase completed. Whether this org still runs a service application, or only ever watched a demo. Which channel, which case, which queue. The announcement answers the first. It cannot see the tenant. The third is service design. Some teams kept a service application running. Some had already moved topics into cases. Some only ever watched a demo. A pack that picks one of those stories for every team will be wrong for at least one of them. **A good answer sounds like** the service director, ticket in hand, saying the announcement settles ownership and the 16 October 2023 close, that nobody present can open a current Airkit.ai screen, and that any build is a named channel and a named queue. **A bad answer sounds like** the product is gone, so we rebuild everything inside Service Cloud this quarter. Every clause may feel true in the room. None of them is checkable. Gone is not a date. Everything is not a channel. This quarter is a template field, not a notice. Then ask whether it is a product problem at all. A queue with no roster, a refund rule nobody can state, and a shipping window that lives in someone's head all present as the old tool having failed. All three remain yours after any rebuild. The announcement did not take them on. ## Who owns Airkit.ai, and who owns the rules? Salesforce owns Airkit.ai. Salesforce completed the Airkit.ai acquisition on 16 October 2023. That is not a partnership, a reseller arrangement, or a rumour still awaiting confirmation. Did Salesforce buy Airkit.ai? Yes. The announcement says the acquisition completed. Salesforce owning the company does not make Salesforce the owner of your case record types, your queues, or your articles. A director who writes that the path will arrive configured has skipped the ownership that changes a Monday morning. Who owns a topic is the person who can change the rule and have it stay changed. The shipping window has an owner. The refund rule has an owner. The queue has a roster. If you cannot name those people, you have a brand, not an implementation. The owner of the brand, after 16 October 2023, is Salesforce. The owner of the rule is the person who can refuse a change to it. The cited announcement does not publish a headcount, a founder statement, or a jobs list. A profile is not the close. A hiring post is not a roadmap. Ask Salesforce who carries the work, or read a page Salesforce publishes for that purpose. Do not staff a service design from a career page, and do not turn a founder's exit into a support plan. Support is a contract and a queue. Why Salesforce acquired Airkit.ai, beyond the placement in Service Cloud, is not a motive you can recover from the completion line, and why the company sold is not stated there. Private reasons are not a scope. **A good answer sounds like** a named service owner who has changed the refund rule or the shipping window since 2023, and who can point at the queue roster for the topic on the ticket. **A bad answer sounds like** Salesforce owns it, so the configuration will arrive with the product. That sentence names the company and then invents an implementation. The cited announcement did not configure your case types. ## What does 16 October 2023 decide? The date is 16 October 2023. Write it that way. The quoted sentence uses the month-first form because that is how the page was published. Both refer to the same day. Do not add a second day because a slide has a spare column. Completion means the acquisition closed. It does not mean your channels changed that morning, that a sandbox appeared, or that a contract line changed, unless your own contract says so. Open the order form for the commercial date. The announcement has the close only. Before that day, Airkit.ai was a separate company building customer-service applications. On it, Salesforce completed the purchase and the announcement placed the work in Service Cloud. After it, the announcement does not narrate a rename, a shutdown, or a price. If a later Salesforce page gives you one, cite that page. A close in 2023 can sit beside a later ticket without becoming a deadline. The age of the announcement is not an end date. **A good answer sounds like** the programme lead reading 16 October 2023 from the announcement, and reading any go-live from the project plan, with the two dates labelled as different documents. **A bad answer sounds like** we acquired it in 2023, so it must be off by now. The year is real. The must is not on the cited announcement, and it is not on the order form unless someone has opened the order form and found it there. ## What may be written in the price cell? The cited announcement does not publish a price, a purchase price, or a licence fee. A blank is an honest cell. A number copied from a recollection is not a cell you can defend when finance asks which document it came from. How much Salesforce paid, and how much the company was sold for, are the same unanswered question. Completion is not a consideration disclosure. If a filing or a later report states a figure, that figure is not on the announcement cited here. Your licence cost is a third number, on your order form. Mixing the three is how a steering pack acquires a price nobody can audit. Do not put a zero in the cell. Zero would mean you know the consideration was nothing. There is no free trial on the cited announcement. If your contract already includes Service Cloud, that inclusion is your contract, not a trial the close created. Name the products you already pay for when the conversation becomes a build, and leave the amounts in the agreement. **A good answer sounds like** the finance partner, announcement open, saying the price cell stays blank, and the order form open only when the question turns to what this organisation already pays for Service Cloud. **A bad answer sounds like** we will put a round number in so the slide has a total, and correct it later. Later is the business case. The number will be the one people remember, and the announcement will not be in the room to contradict it. ## Is there a shutdown to schedule? No end date is published for the acquired capability. There is no sunset date on the completion line, and no switch-off instruction. Do not invent one because a search includes the word shutdown, or because a template has a field called end date. No current screen is described from the announcement. You cannot schedule a retirement it did not publish, and you cannot demo a menu it did not show. If the team still logs into something, the owner of that login answers whether it is in use. Customers are not told to leave Airkit.ai by a deadline. Do not rebuild the old application inside a Case because a keyword says migration. On a risk register, record three lines. No end date is published. No current screen is described. The home named by the announcement is Service Cloud. Then look at the org. The register should send a person to look, not to guess a quarter. ::: warn Do not draw a current Airkit.ai screen, and do not type a purchase price or a shutdown quarter. The cited announcement gives a completion on 16 October 2023 and a home in Service Cloud. Anything beyond that is a local fact someone has opened, or it is an invention. ::: **A good answer sounds like** the service director stating there is no published end date, that the login owner will confirm what still runs, and that 16 October 2023 will not be reused as a sunset. **A bad answer sounds like** we should switch it off this quarter so the programme has an end. The quarter was chosen to fill a template. The announcement did not choose it, and the people who still use the login were not asked. ## What would you actually build? The work, once those lines are accepted, is channels, cases, knowledge, and the queue a person still owns. It is the service path you already run, not a reconstruction of a 2023 interface. A topic spreadsheet is not a price. A list of intents with no channel and no exception path is a brainstorm. Name the channel the customer already uses, the Case fields that record the outcome, the knowledge a person stands behind, and the queue that takes the exception. If the pack still needs a picture, use a table of channels you already run, with an owner against each one. A demo, if you need one, is a demo in your org or a demo Salesforce will show you now. A roadmap is whatever Salesforce publishes, read on the day you read it. The cited announcement does not say customers were forced onto Salesforce. Some teams will have chosen to move topics into Service Cloud. Some will still be deciding. A partner should restate the ownership line, the date, the home, the blank price, the missing end date, and the channel they would pilot before naming a fee. A purchase price, a product screenshot, or a sunset quarter is a proposal to send back. **A good answer sounds like** one live topic, one channel, and the person who receives the exception, with the 2023 demo left out of the pack. **A bad answer sounds like** we will migrate the old application into cases and price the topic list. That spends the acquisition as if it were a statement of work for a menu nobody has opened. ## What to do with the answers Read the six as a set. Specific answers mean any further work can be scoped against a service path you can name. General answers mean the decision rests on a shared feeling that the old login has vanished, which may be true of a bookmark and still says nothing about the org. If the answers are specific, the next discipline is the service path, set out in [Airkit.ai and Service Cloud](/airkit-ai-service-cloud). If they are not, the useful outcome is a shorter list of claims that were about to be blamed on a product the room cannot open. Keep this page for the lines a finance partner will check: owned by Salesforce, completed 16 October 2023, placed in Service Cloud, price not published, no end date, no current screen. ## Questions ### What happened to Airkit.ai after Salesforce bought it? Salesforce completed the acquisition on 16 October 2023 and placed the work in Service Cloud. Airkit.ai built customer-service applications. Releases have landed since that close, so a menu from a 2023 demo is not a current screen. Some teams still run a service application, some moved topics into cases, and some only watched a demo. ### Is Airkit.ai owned by Salesforce? Yes. Salesforce completed the Airkit.ai acquisition on 16 October 2023. That is not a partnership or a reseller arrangement. Ownership of the company does not move your case record types, queues, or articles. The person who can change the refund rule or the shipping window is still yours to name. ### When did Salesforce acquire Airkit.ai? The cited announcement completes the acquisition on 16 October 2023. That date is the close. It is not a go-live, it did not create a sandbox, and it is not a contract anniversary unless your order form says so. The same announcement gives no second date for a rename, a price, or a shutdown. ### How much did Salesforce pay for Airkit.ai? The cited announcement does not publish a price, a purchase price, or a licence fee. Leave the cell blank. A zero would claim the consideration was nothing, which the announcement does not say. There is no free trial on that announcement. What you pay for Service Cloud is on your own order form. ### Did Salesforce shut Airkit.ai down? No end date is published for the acquired capability, and customers are not told to leave by a deadline. No current screen is described from the announcement. If a login still works, the owner of that login can say whether it is in use. Do not rebuild the old application inside a Case because a ticket says migration. --- SynconAI is a Salesforce Select Partner and an OpenAI Select Partner, delivering architect-led Salesforce and AI programmes across the United States and Australia. Related service: Agentforce consulting (https://synconai.com/salesforce-agentforce-consulting).