What you do in the web console

The phone is for doing the work. The console is for configuring it. The split is deliberate: nothing you set up once a quarter belongs on a phone screen, and nothing you do between appointments belongs behind a desk.

Not in the app

• Creating or editing agents, and the instructions that shape how they behave.
• Authoring automation templates, and editing an automation's steps or configuration. The phone can run one, read its runs and answer its approvals, and can request a new one.
• Defining entity types and their fields, and importing records in bulk.
• Granting record access to people or teams.
• Managing knowledge stores and the files in them. The app reads them, to attach a file to a chat or to show what an automation is pointed at.
• Organization administration: members, teams, roles, usage and billing. Your own API keys are an exception and can be generated and revoked from the phone.
• Signal definitions, signal categories and how detection works.
• Analytics dashboards and the knowledge graph.

Where you reach one of these, the app points you at the console instead of showing an empty screen. An automation's step list is the clearest case: it shows exactly what will run and says plainly that it comes from the template and cannot be changed here.

What the app has that the console does not

The traffic goes both ways. Voice notes, and the offline recording behind them, exist because a phone is in your pocket and a laptop is not.

Full console documentation

See Web console for what each area of the browser app does.