Skip to main content
A workspace keeps its assistants, calls, campaigns, knowledge, phone numbers, plan, credits, and billing separate. Signing up creates your first workspace automatically. After signup, a one-time setup screen lets you confirm that workspace’s name, company website, AI inference region, country, timezone, and currency. If you used a business email address, the website is suggested from its domain. Click the logo to upload your own (PNG or JPEG); otherwise, the website favicon is previewed and saved as the workspace logo when you continue, if one is available. Country, timezone, and currency start from your location when available. Changing the country suggests a matching timezone and available currency, and you can still change either field yourself. Currency changes may be restricted after a payment or when a reseller manages the workspace currency. You can edit these settings later under Settings → Workspace. Three short questions follow: what you would like to automate, how many calls you handle per month, and how you heard about us. You can go back to earlier steps until you finish. Your answers help tailor suggestions in the app. You can also join other workspaces and, when your plan allows it, create additional workspaces of your own.

​
Switching workspaces

Select the workspace avatar at the top of the sidebar. The switcher lists every workspace you can access and your role in each one. Choosing a workspace reloads the dashboard with that workspace’s data. Your selection affects only your own session. Other members keep their current workspace.

​
Creating another workspace

Open the workspace switcher and choose New workspace. The dialog shows whether your account can create another workspace and prompts you to choose a name. The number of additional workspaces depends on your plan and the Extra Workspaces add-on — extra capacity bought per additional workspace from Settings → Plan, the same way the other capacity add-ons work. Joining someone else’s workspace does not consume your creation allowance. Existing workspaces remain accessible if your allowance later changes; the limit applies when creating a new one. Each new workspace starts separately, so review its plan and billing before adding production resources. It does not inherit the plan or the credits of your first workspace: a subscription applies to the workspace it was bought in, a new workspace starts at zero credits, and credits cannot be moved between workspaces you own — there is no shared pool to split. Subscribe to a plan or buy a top-up inside every workspace that should place calls. Transfers exist only for white-label resellers funding their customer workspaces, see Credit balances & transfers.

​
Workspace profile

Open Settings → Workspace to view and edit the active workspace’s identity and defaults: its logo, name, company website, timezone, date format, country, and the default language for members who haven’t chosen one themselves. Owners and admins can change these fields; every other role sees the same fields read-only. A new workspace detects its country from the signup or first-use location; an owner or admin can replace that choice at any time. The page also shows the workspace ID — read-only, and the value to quote in support requests and API calls.
Workspace settings sidebar, logo and name fields, timezone and language controls

Settings → Workspace: use Upload logo and Workspace Name for the workspace identity, then review Timezone and Workspace language.

When your billing profile has no address yet, the workspace country is used as the initial billing country for checkout. Existing billing addresses are preserved. Review and complete the billing address during checkout; changing the workspace country does not replace an address already saved in your billing profile. AI inference region controls where Famulor runs the AI processing behind this workspace — the language-model work in conversations and the AI judge that analyses them afterwards. Global lets Famulor’s own routing choose; pinning EU or US keeps that processing inside the chosen zone and narrows the model catalog to what is offered there, so an assistant can only be set to a model available in the region. This is the workspace-level control behind the processing-location commitments described in Trust Center. Pinning either region can raise the cost of that AI usage compared with Global routing.
AI inference region selector with Global selected and EU and US alternatives

Settings → Workspace → AI inference region: choose Global, EU or US for workspace AI processing.

See AI regions & models for the complete model list, EU/US endpoint availability, automatic SIP routing and infrastructure locations. Selecting EU also activates an after-save AI-disclosure review for every assistant. The review checks the consent announcement, the effective opening greeting (including an uploaded audio greeting or caller-first silence path), and opening prompt instructions. At least one effective opening path must clearly tell the caller that they are interacting with an AI assistant. Changing the region re-reviews existing assistants. The Beta features toggle also lives on this page. Several capabilities referenced elsewhere in these docs — connected-app triggers in Automations, WhatsApp Call, and the Beta channel connectors, among others — stay hidden until an owner or admin turns it on. Beta features can be unstable and change, and some process additional conversation context and add AI usage, so review each one before enabling it.

​
Roles and team management

Open Settings → Workspace → Team in the workspace where the person should work. Invitations and roles apply only to that workspace, and a person can hold a different role in each workspace they belong to — owner in one, member or viewer in another. The Team panel always shows the active workspace’s name to help prevent inviting someone into the wrong account.

​
Roles

​
Inviting a member

Owners and admins add a member one of two ways:
  • Invite by email — sends an email with a link to set a password. An existing account is added directly and notified by email instead of getting an invite link.
  • Create with a password — set a name and an initial password (at least 8 characters) yourself, with no email round-trip.
Both modes ask for the new member’s role up front — any role except owner — and show that role’s description as you pick it. A member added by email keeps an Invited badge in the list until they sign in for the first time. Once a workspace reaches its member limit, Invite member is replaced by a link to Settings → Plan for more capacity.
Invite by email form with name, email, role and Send invitation

Settings → Team → Invite member: choose Invite by email, enter the member’s details and Role, then select Send invitation.

​
Managing a member

From a member’s row, owners and admins can:
  • Change role in the row’s Actions menu — select a role and choose Save role.
  • Send a login link — emails a single-use link that signs the member in without a password and expires shortly after, useful when someone is locked out.
  • Remove them — drops their access to this workspace only, without affecting any other workspace they belong to, and leaves their Famulor account itself intact.
The owner’s row carries none of these controls; every other member can have their role changed or be removed.

​
Transfer ownership

The current owner opens the new owner’s Actions menu and chooses Transfer ownership. Review the member and confirm. The previous owner remains an admin. Pending invitees must accept their invitation first. Other admins cannot transfer ownership. Only the new owner can transfer it again. Plan, credits, numbers, and workspace data stay in place. Billing email, address, and payment methods remain unchanged; the new owner can update these through billing settings. Login email and historical invoices are not changed. User-bound API keys and OAuth connections of the previous owner are revoked when their role changes; workspace service credentials remain in place. Team listing, role changes and ownership transfer are available through REST and MCP. Invitations and member removal remain available in the Team panel.

​
REST API

List the workspaces visible to the credential:
Workspace list entries can include a logo and its dark-appearance variant, so integrations can display the workspace identity alongside its name. Create a workspace with a user-authorised credential:
Use settings:read to list workspaces and settings:write to create one. A workspace-only service credential can list its own workspace but cannot create a workspace on behalf of a person. Read or update the country of the workspace bound to the credential:
Reading requires settings:read; changing it requires settings:write. Send null to return to automatic location detection on the next dashboard or sign-in request. Create a dedicated API key for a workspace returned by the list endpoint:
This operation requires a user-authorised credential with settings:write. The credential’s user must currently be an owner or admin in the selected workspace, and the workspace must belong to the same brand as the credential. It works for regular multi-workspace accounts and does not require white-label access. Members, viewers, billing users, and workspace-only service credentials cannot use it. The new key is permanently bound to the selected workspace. Its scopes cannot exceed the calling credential, and it cannot outlive a calling credential that already has an expiry. The plaintext key appears only in the successful response, so store it immediately and do not retry a successful request automatically. A newly created workspace may receive its key before plan activation, but normal API calls with that key remain plan-gated. Workspace-capacity and extra-member add-ons have separate jobs: workspace capacity controls creating additional workspaces, while member capacity controls invitations. Neither adds another requirement after a user already has an owner/admin role in the target workspace.

​
MCP

  • list_workspaces lists the workspaces visible to the connected user.
  • create_workspace creates a workspace when the connected user has remaining allowance.
  • create_workspace_api_key creates a dedicated key for a visible workspace where the connected user is an owner or admin.
  • get_workspace_country reads the active workspace country.
  • update_workspace_country sets an ISO two-letter country code or returns to automatic detection.

​
Message labels

New incoming messages can receive a Possible scam label. Unsolicited sales pitches, SEO offers and paid award promotions in email can receive Advertising. Labels appear beside the message and in the History list after background processing. These are advisory hints and may be wrong. Messages remain visible, replies continue as usual, and no message is moved, deleted or marked as spam in a connected mailbox, including Gmail. No label does not mean a message is safe. Booking and customer enquiries should remain unlabelled. Workspace owners and admins can switch Message labels on or off in Settings → Workspace, when included in their plan. Changes apply to new messages; existing labels remain. Members with write access can dismiss an incorrect label in the message details. History API responses and the history MCP tools include active labels. Use dismiss_inbox_label to dismiss one, and get_inbox_label_settings / update_inbox_label_settings to manage the workspace setting.