For enterprise teams
No SOC 2, no ISO 27001, no BAA, no SSO or SCIM, no published SLA.
Every gap that ends an enterprise review is named on this page in plain words.
Put the list of what is missing in front of the people who have to sign.
A department that can move on its own, yes. A company-wide security standard, not yet.
The cost
Demos, half a questionnaire, then the SOC 2 question — and the answer is no.
0
certifications qallin holds today
The product
What a reviewer dislikes is not the feature list — it is that nobody can explain where a call goes.
A separate number per department, per site or per function
Rules in order — by hour, by who owns the customer, or straight to one person
Out of hours the last rule ends with the caller’s reason written down rather than a beep
A phone system becomes an internal problem because the history lives on handsets.
Calls and texts in the same thread, from the number the customer already has
Internal notes the customer never sees, on the record they belong to
Someone leaving is a permissions change; the conversations stay where they were
The part of a call that has value later is what was agreed and what got sent.
A written summary from the conversation, with the commitment, an owner and a date
The follow-up sent from the number the customer called, not from somebody’s mailbox
Paperwork filed under the customer rather than in a second system nobody searches
Your week
The answers we would send back are already on this page. Decide before you send it.
None. No SSO and no SCIM today — accounts are invited and removed by an administrator.
No published SLA, no uptime commitment, no dedicated support contract.
A team inside a large company, running its own calls, is the honest fit today.
Any size
The product is the same in all three. What changes is how many phones the line rings, and who is expected to pick up.
A team with its own numbers, routing and record, running without waiting on anybody else.
Separate lines per team, one customer record across them. Accounts are still administrator-managed, not directory-managed.
A local number where you have people, kept as one account. It does not yet come with the certification and identity paperwork a company-wide standard asks for.
The fine print
Every line below is what we would put on your questionnaire, before you send it.
Switching
A department alongside your platform, not replacing it, is the realistic shape. Porting is free.
No, neither. There is no report to send under NDA and no audit under way that we are going to promise you the result of. What we can give you is a description of how the thing works and an honest answer to any specific question in your questionnaire.
Not today. There is no SSO and no SCIM — an administrator invites people and removes them, and removal ends access immediately. If directory-managed access is a hard requirement, this is where the evaluation stops.
Nothing, in writing. There is no published SLA and no credit schedule. We are not going to quote a figure to win an evaluation and then be measured against it.
The same as everyone else. There is no dedicated success manager, no named engineer and no response-time commitment you could put in a contract.
That is the case this page is written for. A department with its own numbers and its own record can run without touching the platform decision, and it leaves nothing behind if you decide against us.
A completed audit, identity that your directory manages, an SLA in writing, and a support agreement with names in it. All four are absent today. Tell us which of them your review requires and we will tell you whether we can meet it — or that we cannot.
Waitlist
Send the questions, and we will answer each with yes, no or not decided.
From RingCentral
From Dialpad
From Vonage