With multi-store, one Consio workspace can hold more than one store. Each store represents one of your brands or storefronts — for example a US store and a UK store, or two different brands your team supports.
You'll find your stores in Settings, in the Stores section of the sidebar. Each store has its own page where you manage everything that belongs to it, and the + button next to Stores adds a new one — see Adding a store.
What belongs to a store
Each store's page shows everything attached to this store:
Phone numbers — manage numbers for calls to and from this store. Each number can be linked to a store, and the store carries a default Caller ID name (CNAM) — the name that appears when you call.
AI agents — AI agents that make and answer this store's calls. An AI agent uses its store's orders, products and knowledge, and only answers that store's numbers.
Knowledge base — the content your AI agents use to handle conversations. Knowledge can belong to one store or to All stores.
Product catalog and Discounts — the products synced from Shopify and the discounts linked to this store.
Integrations — the store's own Shopify and Klaviyo connections.
Store timezone and Business hours — used for this store's business hours, callbacks and analytics.
Campaigns — a campaign is assigned to a store and pulls segments from that store's integrations.
What stays at the workspace level
One login for your whole team. Everyone signs in once and works across stores from the same place.
Your team. Agents and teams are not locked to a store — one agent or team can be in the routing for phone lines across all your stores.
Your help desk. Gorgias, Re:amaze and other help desks connect once per workspace (they show a Workspace badge on the store page), so brands living inside one help desk account stay reachable.
Your plan and billing. One workspace, one plan.
When multi-store is the right fit
Separate brands. You run two or more distinct brands, each with its own Shopify store, policies, and voice. Each brand becomes its own store with its own phone numbers, AI agents, and knowledge — even if the same team answers for all of them.
Separate regions or countries. A US store and a Canada store, or regional storefronts with different currencies, business hours, and timezones. Each store sets its own hours and timezone, and each country gets its own local number.
Brands that should not look related. Every store keeps its own numbers, AI agents, and knowledge base, so each brand presents itself on its own — its own caller ID, its own voice, its own policies.
One team, many storefronts. Your agents keep one login and work across all stores — contacts, inbox, and dialing in one place.
When it is not
One store that wants one AI agent to handle different kinds of data. Multi-store separates data by store; it does not let a single store split its own data into compartments. If that's your situation, talk to us about how to structure your knowledge base instead.
One shared public phone number with AI answering for several stores. An AI agent belongs to one store, so a single number can't give AI full context for several stores — use an IVR to route callers to each store's own line instead (see Phone numbers, AI agents, and knowledge per store).
If you only have one store
Nothing changes for you. Your phone numbers, knowledge base, and AI agents are associated with your one store by default.
A good way to think about it: multi-store is an organization upgrade, not a merger. Your stores stay separate — separate numbers, separate knowledge, separate data — but your team manages them under one login.