Operations with Aria

Aria leads Operations. Use Aria to organize incoming work, make ownership visible, track service commitments, and coordinate follow-up without losing the original request.

Start with the operating rules#

Complete Aria's guided setup and keep stable process facts, service rules, escalation paths, and approved decisions in Memory. Include temporary deadlines, customer circumstances, and exceptions in the relevant item rather than turning them into permanent instructions.

Triage work in the Operations Inbox#

The department Inbox holds incoming operational threads. Open a thread to review its source, content, status, urgency, and next action. Marking something urgent should reflect your operating rules, not simply the tone of the message.

Ask Aria to summarize and classify before acting when the request is ambiguous:

Triage these new requests. Mark urgent only when the customer is blocked today. Draft the next step, but do not send a reply.

The department Inbox is for operational intake. The main Winglo Inbox and approvals brings together decisions and approvals from across the workspace.

Manage leads and follow-up#

Leads provides a working list for operational follow-up. Confirm the source, owner, stage, and latest contact before changing a record. A lead entry is not proof that consent, qualification, or outreach permission exists.

Avoid creating duplicate follow-up when an earlier external result is unclear. Check the connected provider before trying again.

Watch service levels#

SLA helps identify unanswered work that is approaching or past a service target. Open the underlying thread before escalating it. Confirm the relevant time zone, business hours, pauses, and source freshness.

An SLA warning points to timing risk; it does not determine the correct business response.

Use Calendar, Live, and Collaborations#

Calendar shows scheduled operational work. Review dates and time zones when creating or moving an item. Live shows work currently in progress. Collaborations holds structured requests or handoffs that need review or coordination.

When assigning work to another department, include the owner, expected result, deadline, and constraints. A handoff does not approve an external action.

Connect forms and email safely#

Aria can receive supported form or email intake when it is configured. Copy addresses, URLs, and signing details only from the authenticated setup screen. Treat any secret shown there as a credential and store it through your approved secret manager.

Read Operations intake with forms and email before sending live submissions.

Review reports and integrations#

Use Reports for completed operational analysis and Integrations for the services Aria can access. Confirm connector health and department access when incoming data stops or a proposed external action fails.

Manage Aria#

Use Settings for the controls available to your workspace and Memory for reusable operating context. Pausing Aria stops new department work but may not cancel work already running, so also check Workflows, Live, and connected providers.