Skip to Content

Use cases

Enterprise

Plans across every team, approved by the right people — with private plans kept private.

WebiPhone

For operations, travel and executive teams coordinating people across departments and locations. One change reaches several teams at once, each with its own approver, budget and details the others shouldn't see.

Organization overview with workspace counts, waiting approvals, double-bookings and plans coming up across teams, including a private plan

Example: an office closure

Arcwell Group runs a Sales team, a Field operations team and an Executive office, each in its own workspace. The Berlin office closes on the 29th.

The organization view shows who's affected: the Sales summit's second day (42 people), a Field operations training (9 people) and one private Executive office plan. Each team's approver hears about it. The private plan shows only that it's affected — never what it holds.

Try asking

You: The Berlin office is closed on the 29th. Who's affected?

Nuri: Three teams: the Sales summit's second day (42 people), a Field operations training (9 people), and one private Executive office plan. I've told each team's approver; the private plan's details stay with its owners.

What matters most

Policies the plan already knows

Hotel limits and approval thresholds apply as plans are made. Exceptions go to the approver who owns them. See Rules and approvals.

Roles and workspaces

Teams work in their own workspaces. Operations sees outcomes across them, and private plans stay private. See Organization.

Every approval on record

Approvals and audit entries are kept for the organization, so an edited or removed entry shows.

Start with one workflow

Most organizations begin with one team — executive travel or crew logistics — then expand.
SettingRecommendation
OrganizationOne organization with a workspace per team or office. Organization roles: Owner, Admin, Billing, Auditor or Member.
Workspace kindsExecutive for the executive office; Events, Production or Something else for other teams.
Word for plansPlan, or a word per team — Trip, Meeting, Offsite.
RolesCoordinators as Managers in their team's workspace; everyone else as Members or Contributors.
RulesOne organization policy, plus approvers per team or threshold.

A typical rollout

Week 1: map one workflow

Teams, approvers and the systems you use today.

Week 2: set up workspaces and roles

Create the organization, its workspaces, and roles.

Week 6: review with your team

Expand to more teams, or adjust.

Enterprise plan

Enterprise adds SSO, SAML, SCIM, custom data retention and an SLA, and includes security reviews and procurement support. SOC 2 Type II and ISO/IEC 27001 are in progress — see Security. Specific controls and terms are agreed with each organization.

On this page