Getting Started with Call: Account, Setup and First Test Call
A practical first-day guide to Call: create a workspace, learn the screens, set business hours and a first call flow, then test it before real callers arrive.
Most phone systems feel complicated for the first hour and obvious by the end of the first week. The difference is rarely the software. It is whether the first day was spent on the right things in the right order. This guide walks through a sensible first day with Call, a cloud call-centre system, from creating an account to running your first test call.

It is deliberately practical. You will see what to decide before you click anything, what a minimal setup looks like, how to test it safely, and how to keep a small record so the next person can follow what you did. For the bigger picture of moving a team onto a new phone system, see Contact Center Digital Transformation in 5 Steps.
What Call lets you do
Call covers inbound and outbound calling, phone menus (IVR), queues, a dialler, quality and workforce tools, AI call summaries, a customer record (CRM), a shared inbox and appointments. You do not need all of that on day one. Most teams begin with the part that answers the phone and add the rest as they need it.
Pieces you will meet on day one
- Phone linesA line holds a number, business hours, who callers are put through to and whether an AI agent answers.
- Business hoursWhen a caller who asks for a person can actually be put through, and what happens outside those hours.
- QueuesWhere waiting calls are held and who is offered them.
- Setup wizardA guided path that takes you step by step from nothing to a line that answers.
- Call historyA record of calls, with recordings and transcripts where they exist.
- Help buttonShort how-to articles for the screen you are on.
Step one: create your workspace
You sign up from the home page. You give your name, business name and type of business, a work email and a password of at least eight characters, then confirm your address from the email that arrives. A new workspace starts with the setup wizard, and a new account starts in Easy mode, which shows a shorter menu.
If you only want to look around, there is also a read-only demo with sample data. Nothing you press there is saved, which makes it a safe way to learn where things live before you commit to a setup.
Step two: learn the screens before you change anything
Spend ten minutes just looking. The sidebar groups the product by job: Home for setup and your shift, Settings for lines and numbers, Calls for queues and live operations, Help desk for callers who asked for a person, and areas for AI agents, sources and reports. Easy mode hides much of this under a few headings; Full mode shows everything.
Two habits save time later. First, use the help button on any page: it opens the how-to article for the screen you are on. Second, check Home for the setup checks. It lists which steps are still open, such as hours not set or the AI agent not yet switched on, and links straight to each one.
Step three: set up the minimum
The minimum for answering calls is a line, business hours and a decision about who picks up. Everything else can wait.
A minimal first setup
- Get a number or connect oneRequest a phone number if you have none, or connect a number you already use. A real call reaches you only when the number is routed to the line.
- Create the line and set hoursChoose the timezone, the opening and closing times for each day, and copy Monday's hours to the other weekdays if they match.
- Choose who is put throughTick the people or saved numbers that should ring when a caller asks for a person, and how long they ring.
- Decide how calls are answeredEither your team answers, or an AI agent answers using a small knowledge base you write.
- Test, then switch onRun the test calls, fix what you hear, then turn the line on.
If you want an AI agent to answer, keep its first knowledge base small: your services, hours and the ten questions callers ask most. The ideas in an AI receptionist setup checklist apply here, and Using Knowledge Sources in Call explains how to add and check sources.
Step four: test before real callers do
Testing has three levels, and it is worth doing all three. Talk to the line on screen first; it costs nothing and shows whether the answers make sense. Then call your own phone from the line to hear what a caller hears. Finally, ring the number from a different phone, as a caller would.
- Listen for the greeting: is the business name clear and the pace calm?
- Ask for a person during business hours and again outside them. Both should end somewhere sensible.
- Ask a question the knowledge base does not cover. The agent should say it does not know, not guess.
- Check that the call appears in call history afterwards.
Good first day vs rushed first day
| Good first day | Rushed first day | |
|---|---|---|
| Scope | One line, one set of hours | Every feature switched on at once |
| Testing | Screen, own phone, outside phone | First real caller is the test |
| People | One owner, then colleagues invited | Everyone invited before anything works |
| Records | Short change log kept | Nobody remembers what was changed |
What to do after the first day
Resist the urge to add features for the first week. Listen to real calls, read the transcripts and note where callers were confused. Then pick one improvement at a time: a clearer greeting, a better answer, a phone menu. When you are ready for a menu with business-hours routing, read Setting Up IVR and Business Hours in Call; for the AI side, see Setting Up an AI Agent in Call.
End-of-day-one checklist
- Workspace created and email confirmed
- Business hours and timezone saved
- Someone chosen to take calls when a caller asks for a person
- Three kinds of test call completed
- Greeting wording written down
- Colleagues and their roles listed, to invite next
- Next improvement chosen
Roles, notes and handover
Even a two-person team benefits from naming an owner for the phone setup. That person decides changes, keeps a short log with the date, what changed and why, and is the one who gets asked when a caller reports a problem. Managers can change lines and queues; ordinary members can usually only use them. Invite colleagues once the minimum works, so they learn a working system rather than a half-built one.
A change log can be a single shared page. Write the date, the line, what changed and how you tested it. When something stops working, the log is the first place to look.
Doing it in Call
In Call, the quickest route is Home, then the setup wizard. It walks through the phone line and business hours, your agent's voice, the prompt, the knowledge base, who to put through, a test, and finally switching the agent on. Until the agent is on, calls ring your team. The Home page also lists any open setup checks and links to each. Call does not provide Japanese phone numbers, so if you operate in Japan, connect a number you already have; the demo lets you try the flow on screen either way.
Frequently asked questions
How long does the first setup take?
A minimal setup, with hours, a line and a small knowledge base, can be done in a working session. Testing and tuning usually take longer than the clicking, so leave time for them.
Do I need an AI agent from the start?
No. You can begin with business hours and a team that answers, then add an agent and a knowledge base when you are ready. Adding it later is often the safer order.
Can I try Call without signing up?
There is a read-only demo with sample data. You can look around, but nothing is saved, so it is for learning rather than setting up.
Will test calls show up in my reports?
Test calls made from the browser are not listed as real calls, but real-phone tests are real calls. Note them down so you can tell them apart later.
When should I invite colleagues?
Once the minimum setup works. Inviting people early means they learn a system that keeps changing underneath them.
What should I read next?
Set up a phone menu and business hours, then an AI agent and its knowledge sources. Each has its own guide in this blog.