Start with the conversation you need.
Write down who needs to talk, which devices they use and whether the call is one-to-one or a group meeting. ImiCall supports two-person browser conversations; it does not dial telephone numbers or provide a shared team directory.
A small agency may want a dedicated line for project check-ins. A distributed team may prefer a lightweight browser workflow. If your existing tool already fits, switching may add work without enough benefit.
Decide who owns the deployment.
Using the public beta is different from operating a private deployment on your own domain. A private setup requires hosting, a relay provider, updates and somebody responsible when a device cannot connect.
For an ImiCall paid pilot, use infrastructure accounts owned by your organization. Keep billing and operational enquiries separate from private invitations and conversation data.
Test the actual devices before buying a rollout.
Keep both browsers open, with one person on Wi-Fi and the other on mobile data. Verify audio in both directions. Repeat using the actual iPhone, Android or desktop browsers your team expects to use.
Test what happens after microphone permission is denied, after a network changes and during a longer call. A working homepage or a successfully issued TURN credential is not enough evidence of reliable audio.
Budget for support as well as servers.
Ask what the setup fee covers, how much support time is included and who pays for relay usage. A small server bill does not include the time needed to diagnose device permissions or network restrictions.
ImiCall introductory private pilots start from US$149 for an agreed small scope. Optional care starts from US$29 per month. Hosting, domain registration and TURN usage are additional; the written quote on the private-setup page defines the final scope.
Agree on acceptance, not broad guarantees.
Choose a small list of pass/fail checks and a named pair of test devices. Record the operating systems and networks used, without collecting call content. Expand only when the pilot meets the agreed criteria.
Do not assume that a private deployment means complete anonymity or compliance with every industry rule. A participant can record, and network operators still process metadata. Keep a fallback communication channel.
The ImiCall walkthrough · Privacy, explained · Private setup & pricing · Testing & limitations