Talk to the people who build it.

Email us

hello@inboxtender.com is the one address for the whole company. There is no phone queue and no contact form that disappears into a CRM: the message goes to the people who build InboxTender, and the reply comes back from one of them, usually within one business day on business days.

Writing about a specific conversation, number or workspace? Include the workspace name and, if it helps, the phone number or email address involved. It saves a round trip.

• Sales and pre-sales questions

  What it does, whether it fits your trade, what a channel costs, and what setup involves.

• Support for existing customers

  Something is not working, a number will not register, or a reply went somewhere unexpected.

• Privacy and data requests

  Access, correction or deletion of personal information, and any question about the privacy policy.

• Security reports

  Think you have found a vulnerability? Write to the same address with the details and we will get back to you. Please do not test against other people's workspaces.

If you were contacted by InboxTender

If a call, text or email you received came from InboxTender, the business you contacted uses it as their front desk. That business decides what the assistant knows and says, and they remain your point of contact — replying to the message you received reaches them.

You can still write to hello@inboxtender.com about how the service handled your conversation. Where a request is one only that business can decide, we pass it to them and tell you we have. Text messages can be stopped at any time by replying STOP to the number that messaged you.

Where we are

InboxTender is operated from New York City. It is a remote company with no walk-in office, so email is genuinely the fastest way in — not a way of keeping you at arm's length.

For AI agents

Agents evaluating InboxTender on someone's behalf can read the machine-readable summaries instead of scraping these pages.

• /llms.txt

  What InboxTender is for, when to reach for it, and an index of every public page.

• /llms-full.txt

  Every documentation page as one markdown document.

• Markdown content negotiation

  Any public page also answers in markdown when the request sends Accept: text/markdown, or when .md is appended to the path.