Our mission
Make customer email the easy part of running a business.
InboxPilot drafts replies in Gmail and Outlook from a company's own documents and tools. By default, someone on the team reads each draft before it goes out.
Where it started
InboxPilot started in July 2024
Samih Sghier wrote the first line of code that month. The product had one job from the start: find the answer to a customer's email in the company's own documents and have a draft ready in the thread before anyone opens it.
The first version launched on December 20, 2024 and worked in Gmail and Outlook. It has since learned to read orders from Shopify, records from Pipedrive, pages from Notion and rows from Google Sheets, and to post drafts to Slack, where a team can send, claim or close them.
Samih still writes most of the code. Taimoor Niazi looks after sales, and Alexandra Swan looks after growth.
“Most of the email a business gets is a question it has already answered. We built InboxPilot so nobody has to write that answer twice.”
Samih SghierFounder, InboxPilotWhat InboxPilot does with your email, and what it doesn't
Nothing is sent until you decide
Drafts wait in the Gmail or Outlook thread until someone on your team sends them. Auto-send stays off until you turn it on for a type of request you trust.
Answers come from your own material
Drafts are written from your documents, website and past replies, and from the tools you connect. When the answer isn't there, the email goes to a person instead of a guess.
Your email isn't training data
What arrives in your inbox is used to answer it for your team and nobody else. How it's stored and who can see it.
Your team can work it from Slack
Matching email posts to a Slack channel with the draft in the thread. Send it, claim it or close it there, and the thread shows who has it.
Start with the emails you’re tired of.
Connect Gmail or Outlook and see your first drafts today.
No credit card. Nothing sends without your approval.