Contact
Email, and we read it.
Four routes below. There is no phone tree, no ticket queue and no chatbot in the corner of this page. If you already have an account, replying to the address in your welcome email works just as well as any of these.
One address per kind of question.
Product questions
Does it work with our setup, what does the Ringba connection actually pull, how do you count revenue, is our volume too low to bother. Pre-sales scepticism welcome. Bring your numbers and we will tell you if the answer is no.
hello@saas.65.21.85.184.sslip.ioSecurity
Vulnerability reports, questions from your security review, DPA and subprocessor queries, deletion requests. Include what you did and what you saw. Please do not test against another workspace's data.
security@saas.65.21.85.184.sslip.ioBilling
Invoices, plan changes, annual terms, cancellations. Cancelling does not require a conversation with anyone. There is no retention script and no exit interview, and your export stays available on the way out.
billing@saas.65.21.85.184.sslip.ioPress and partnerships
Interviews, data requests, integration partnerships. We will talk about the category and about our own methodology. We will not hand over customer call data for a story, under any framing.
press@saas.65.21.85.184.sslip.ioHonest, since we are new.
- No response-time guaranteeWe are not going to publish a number we cannot hold to yet. When we can commit to one, it will appear here with a date next to it.
- No support rota, no tiersYour email does not get triaged into a queue and forwarded to someone who has never opened the product. The people building it read these.
- Silence is a bugIf a message goes unanswered, send it again. That is not nagging, it is useful signal that something in our routing is broken.
- Say what you runCall platform, rough monthly call volume, verticals, and whether your calls are recorded. Three lines of that gets you a real answer instead of three emails of discovery questions.
Faster than emailing
Most pre-sales questions are already answered in writing. The docs cover the API, the MCP server and the connection setup. The methodology page covers the question we get asked hardest: which field we treat as revenue and how duplicates are handled.