Laureo works across the whole product, so a list of every individual thing it can do would be a thousand lines long and out of date by the time you finished it. This page describes the reach by area instead, using the same names the sidebar uses. If an area is listed here, the way to find out what Laureo can do in it is to ask in plain words.

Searching people, companies and deals; creating and updating them; tagging, assigning and archiving; moving a deal through its pipeline and keeping its line items right; company hierarchies, territories, lifecycle stages, contact groups and contact roles; and reading the engagement history behind a record. It can also tell you what a delete would take with it before you commit to one.

Your task list and the queue of things waiting on you; creating, moving, cloning, snoozing and completing tasks; comments, dependencies, reminders and logged time; task templates. Projects, project templates, status updates, share links and the delivery rollup, including turning unbilled time into an invoice. Your calendar: what is coming up, creating and rescheduling events, replying to invitations, and searching across it. Meeting recordings: summaries, transcripts and the action items in them.

Creating and editing booking pages, checking a page address is free, and turning a booking link on or off. Availability schedules and one-off overrides. Who hosts a meeting type and which resources it needs. Previewing the slots a page would actually offer, listing and searching bookings, routing forms, and the single-use access links you hand to a guest. Scheduler defaults for the whole organization are here too, for whoever is allowed to set them.

Drafting an email, rewriting a passage you already wrote, suggesting a short reply, summarizing a long thread, and sending. Scheduled sends, saved drafts, labels, folders, thread comments and thread sharing. Bulk actions across a selection, tracking events, and a pre-send check before a big one goes out. It can also recommend a send time, and tell you whether your own auto-reply is currently on.

Campaigns: drafting audience and copy, previewing, scheduling, pausing, resuming, test sends, A/B variants, follow-up stages, performance and influenced revenue, sending health, and the suppression and unsubscribe lists. Cold outreach: sequences and their steps, enrolling leads, launching, pausing and archiving, sending mailboxes and their DNS checks, tracking domains, send rules, lead lists and lead imports, and the outreach analytics behind all of it. Compliance settings on both planes are readable and, for whoever holds the permission, changeable.

The product catalogue, prices, price tiers, bundles and categories. Quotes: drafting one, line items, versions and revisions, expiry, approval submissions and decisions, deposits, the PDF, and turning an accepted quote into a project. Invoices: creating, sending, editing, voiding, reissuing, milestone invoices, statements and the PDF. Payments: recording one, pay links, payment schedules, refunds and the payment analytics. Collections: the overdue worklist, dunning sequences and enrollments, payment promises, and the collections figures behind them. The goods lane is here too: stock levels and movements, locations, transfers and adjustments, purchase orders and receiving, vendors, sales orders and shipments.

Four things in the goods lane are deliberately not part of that reach: product variants, serial numbers, reserving stock against a sales order, and recording a return. The product ships no screen for any of the four, and Laureo is never given something you could not do yourself, so it will tell you it cannot.

Tickets: triage, routing, assignment, status, snoozing and reopening, drafting and posting replies, internal notes, followers, macros, merges and bulk actions, plus the workload and inbox counts behind a queue. Queues and service level policies. The knowledge base: articles, categories, snippets and variables, article review and verification, revision history, and the help centre settings that publish them. The quality surface as well: scoring rubrics, scores, disputes, and the AI Customer Support Agent's sources and resolution log.

Team chat: reading conversations and threads, searching messages, sending, replying, editing and deleting your own, reactions, pins and bookmarks, direct messages, deal rooms, membership and conversation settings, muting a sender, and turning a message into a task or linking it to a record. Posting a message reaches a colleague straight away and cannot be recalled, so it shows you the conversation and the wording first.

Text messages, WhatsApp messages and phone calls are not something Laureo does, on any plan and in any role, even where your organization has connected a telephony provider and you can send them yourself. They are outside the assistant on purpose, so asking for one gets a plain no rather than a message nobody can recall.

Building and running reports, drilling into a result, explaining what a report is actually showing, exporting it, and scheduling one to be delivered. Dashboards and their layout, pipeline summaries, response times, win and loss analysis, and the daily brief. Goals: creating them, tracking progress, contributions, and the leaderboard along with its visibility policy.

Listing automations and workflows, creating and editing them, turning them on and off, testing a draft before it is live, versions and restoring one, run history and a single run's trace, retries, templates, and the portfolio and health views over the whole set. It can also raise an approval request through an automation and act on one waiting for you.

Your own: profile, notification preferences, inbox and email settings, calendar and sync settings, dashboards and their layout, list columns and view preferences, sidebar and mobile navigation, push devices, and your leaderboard preferences. The organization's, for whoever holds the permission: name, exchange rates, brand tone, dashboard defaults for a role, and whether members can see organization usage. Ask it to change a preference in words and it will show you what it is about to set.

The workspace time zone is the one organization setting it can read but not change. No screen in the product sets it either, and Laureo is never given a change nobody can make by hand.

Inviting teammates one at a time or in bulk, resending and revoking invitations, and the admin overview. Roles: creating, editing and deleting them, and reading what one grants. The credential surface as well: API keys, lead capture keys, and outbound connections with their delivery history. Rotating the organization's encryption key is not among them: it re-wraps every stored secret the organization holds and no screen in the product asks for it, so it is withheld from the assistant rather than offered.

The security surface sits here too, and half of it is about your own account rather than the organization's: your sign-in activity, your active sessions and signing one out, your multi-factor factors, changing your password. For an administrator it extends to everyone's sessions, the session timeout policy, forcing a password reset or multi-factor enrolment, the security audit log and verifying it, and the support access and impersonation status.

Trust accounts and their ledger, recording a deposit, creating a deposit link, applying and reversing a drawdown, preparing a disbursement and deciding one. This area is administrator-gated by default, so most people will not see it at all. Money leaving an account is never automatic: it is prepared, then decided by a person.

Exports of the lists you can already read, import history and the state of a running import, the recycle bin and restoring from it, saved views and collections, tags, custom fields, and the privacy requests your organization has to answer. A commit that writes thousands of rows is treated as what it is: it shows you what it is about to do and waits.

Ask where do I set up booking pages, take me to the vendor list, or what can I do from here and Laureo answers from the real list of pages you can open. That list is filtered exactly the way your sidebar and your command palette are filtered, so it will never point you at a page your role, your plan or your setup does not give you. When you accept, the app navigates and the conversation comes with you.

Two lists can also be opened already narrowed, because those two read the filter out of their own address. Ask show me my customer companies or show me the churned companies and the companies list arrives filtered; ask show me the won deals and the deals list arrives on that stage. It is the table layout of each list that arrives filtered: the deals board and forecast and the companies lifecycle board do not read a filter from the address, so asking for one of those AND a filter is refused rather than opened with the filter quietly dropped. Any other page, or any filter a list does not have, is refused by name too, so a link Laureo hands you never claims a filter it did not apply.

Moving you to a page changes nothing, sends nothing and shows you nothing you could not already reach by clicking, so it does not raise an approval card. Your browser's Back button is the whole undo.

Ask how does the scheduler work or what is a suppression list and Laureo searches these articles, reads the one that answers you, and replies in the product's own words with a link to the article it used. It can also list the sections of the help centre if you would rather browse. That is the difference between an assistant that describes your product and one that describes a product in general.

One group of guides works differently. The moving from guides under Import and export are assembled from the live import settings at the moment you open them rather than written out in advance, so Laureo can find them and link you to them but cannot quote them back. For those you get the link and a note saying to open it.

Reading and drafting happen straight away. A change produces an approval card naming the exact fields it is about to write, with Approve, Deny, and Edit where the card has editable fields, and whether it can be undone afterwards. Some changes are a single nested list rather than a set of separate fields, and there Edit has nothing to offer, so it is not shown. A missing detail produces a clarification card that collects every open question at once instead of interrogating you field by field. Both are covered in Using the Chat.

Which individual actions are allowed to run without a card is an organization setting, not a personal one. An administrator sets it in Settings, Company, Integrations, AI, where actions are grouped by the part of the product they belong to. Until it is changed, everything asks first. Sending, publishing, spending, deleting and changing permissions always ask, on every plan and whatever that setting says. Approval settings covers it in full.

Every action in the product is classified, but not every one has an assistant capability behind it yet. When you ask for something in that gap, Laureo names the boundary and points you at the page where you can do it yourself, rather than improvising. The same is true of anything that requires you personally: entering a credential, clearing a multi-factor prompt, granting consent to an outside provider, or proving your identity to one.