Tasks

Tasks is where ArcGlass turns work from everywhere into one owned, dated list, and then drives each item to closure. Commitments and next steps from meetings and email, playbook questions still to ask, outreach steps, meeting prep, deal moves and message fixes all become tasks, each with the words or the reason that created it. ArcGlass removes duplicates, finds the owner, puts each task in front of that person at the right moment, closes what the evidence shows is done, keeps closed work closed, and keeps every person's list short enough to finish.

Key facts

• What it is: one list of what your team still owes customers, prospects and each other, built from the work ArcGlass already sees. Every task is driven to an end state: done, dismissed with a reason, merged into another, or handed to whoever is responsible.
• Nobody types tasks in. Tasks come from meetings, meeting notes, email threads, playbooks, Pursuits, Engage, Messaging and imports. You can add one yourself, but you rarely need to.
• Evidence on every task: the exact words that created it, and every later mention, each linked to its source. A task an engine created, such as an outreach step, carries the rule and the sourced fact behind it instead.
• AI proposes, people decide. ArcGlass creates, merges and retires its own suggestions. It never closes a task a person accepted, edited or assigned; it asks.
• Closed from evidence: when a later email shows a commitment was kept, or a later call covers a playbook question, ArcGlass closes the suggestion or asks the owner to confirm.
• One queue for the day: Today ranks everything you own across every account, sized to the number of actions you can do, with a guided session to work through it.
• A short list by design: each person's working list aims for 15 tasks or fewer. Task Sweep clears a backlog in a few minutes, and its decisions can be undone for 30 days.
• Who it's for: account executives, customer success managers, founders, and every manager who needs to know what was promised and whether it happened.
• Where: Tasks in the console's left navigation, and the Tasks tab on every account.

Not a to-do app

A to-do app holds what you remember to type. Tasks holds what your team actually said it would do, and keeps going until each item is closed:

• Captured, not typed: from conversations ArcGlass already analyzes, and from the engines that run your outreach, deals and messaging.
• Curated, not complete: the raw backlog can run to thousands of rows. Each person sees the small set that earns attention; the rest stays searchable.
• Evidence, not opinion: every task shows why it exists, so anyone can check it.
• Closure, not storage: a task isn't finished when it's written down. It's finished when it's done, and ArcGlass keeps track until it is.

Questions it answers

• What did we promise this customer, and did we do it?
• What do I owe people today, and how long will it take?
• Who's waiting on us right now?
• Which commitments from last week's calls are still open?
• What does the customer owe us?
• Which tasks look done, so I can close them in one click?
• What do we still need to ask this account on the next call?
• Across the team, what's open, overdue or without an owner?

The life of a task

Every task follows the same path, whatever created it:

1. Captured. A conversation, an engine or a person creates it, with its evidence.
2. Matched. If the same task already exists, the new mention joins it instead of creating a copy. A task raised in a meeting and chased over email is one task with two mentions.
3. Judged. Within minutes, ArcGlass works out how firm the commitment is, who owns it, how clear and important it is, and whether someone is waiting.
4. Owned. It gets an owner on your team, or a suggested owner for you to confirm.
5. Surfaced at the right moment: in Today, in the account's Tasks tab, in the morning brief and in the weekly reminder.
6. Worked: done, snoozed, reassigned, blocked with a reason, or followed up with a drafted email.
7. Closed: by a person, by the engine that created it, or by evidence that it's done.
8. Kept closed: a later mention of finished work attaches to the closed task instead of reopening it, unless it says the work is still open.

Where tasks come from

Conversation tasks come in four kinds: a commitment (a promise, with an owner and a date), a next step (what was agreed to happen next), a follow-up (something to chase) and a risk (a problem someone flagged).

What counts, and what doesn't

ArcGlass is deliberately strict about what becomes a task:

• Only our side's work. Something your team must do becomes a task. Something the customer committed to goes to What they need to do, not your queue. Shared work keeps your half.
• Firm commitments over vague ideas. Each item is graded from an explicit commitment, through an explicit request and an agreed next step, down to an inferred follow-up, a suggestion, a vague possibility or passing information. The weak end rarely reaches anyone's list.
• Unowned gaps roll up. Things an internal meeting noticed but nobody took on become one row per meeting, "Unowned from (meeting): N items", each with its quote.
• Playbook questions stay questions. Missed playbook steps become one checklist per account, "Ask on the next call", with a line per step and its source meeting. It stays in Suggested and on the account page, never in Today, because nobody promised it. Each line ticks off when a later conversation covers the step, and the checklist closes when every line is ticked.

Two kinds of task

An engine task's evidence reads, for example: "2nd touch to Priya, economic buyer. Why now: Acme opened a Denver office (verified, with source)." Tasks you create yourself start open and go straight to your list.

How each task is judged

Within minutes of arriving, every conversation task is judged, and judged again every 4 hours:

• Commitment strength: explicit commitment, explicit request, agreed next step, inferred follow-up, suggestion, vague possibility, informational, or risk.
• Ownership: ours, theirs, both, or unclear. Only ours, and our half of shared work, can be a task in your queue.
• Quality and importance: how actionable, specific and clear it is, who it depends on, how commercially important and urgent it is, and whether it still matters today. How often it has been mentioned, and whether it has an owner and a date, count too.
• Customer waiting: whether a customer is waiting on us, such as "can you send…" or "we're waiting on…" in their email.

The answer decides where the task sits: in What we need to do, in Suggested, in What they need to do, or hidden with its evidence kept. A task with unclear ownership stays in Suggested until someone confirms it.

Evidence on every task

A task with no evidence is treated as a bug. Every conversation task carries the verbatim phrase that raised it, and every re-mention adds another, so a task shows its own history: "Raised in the Jun 30 QBR · still open in the Jul 8 sync · chased by email Jul 12."

• Open the source at this phrase. For a meeting, the transcript opens at the quote; for an email, the message opens at the quote.
• Mentioned N times — see where. A count shows how often the task came up, and opens each mention.
• Raised in (meeting). Open the meeting. Every task links back to where it started, with when it was first raised and when it was last mentioned.
• Edits stay yours. An edited task shows Edited. If ArcGlass later suggests different wording, the evidence view says so, with Use this wording if you want it.
• Every change is recorded, with who made it: a person, Task Sweep, the scoring pass, or the engine that owns the task.

Owners

• An owner is always someone on your team. A customer who made a commitment is never the owner of a task. Each card shows the Accountable owner (click to reassign) and who committed, for example "“Dana” committed".
• Assigned only on a sure match. ArcGlass sets the owner when the person named in the conversation matches a teammate exactly. A weaker match, such as a first name or "their CTO", shows Assign to (person)? instead. A wrong owner is worse than none, because the task silently drops off the right person's list.
• Needs owner. Tasks without an owner are marked and counted, so somebody picks them up.
• Outreach goes to the doer. A pursuit's team roles (Owner, LinkedIn, Email and Phone call) assign each step, so a call lands with the caller.
• Due dates stay honest. You can't move a due date into the past, and ArcGlass drops past dates a conversation mentions rather than filing work as already overdue.

One task, not five

The same commitment gets mentioned again and again, in new words, across meetings and email. ArcGlass keeps it as one task:

• At creation: an exact repeat joins the existing task. A paraphrase is compared by meaning with the account's open tasks: a near-certain match joins automatically, and a possible match is checked by AI before it joins. Internal work is compared with the same owner's, or the same recurring meeting's, open tasks.
• Every night: a merge pass folds untouched duplicate suggestions into the older task. The merged task is kept, not deleted, and its mentions move to the survivor.
• Folding: tasks with the same objective on one account fold into one card, "+N related folded in". Folds last, and can be undone.
• Closed stays closed. A new mention that matches a task closed in the last 60 days, whether it was done, dismissed or merged, attaches to the closed task instead of creating a new one. It reopens, as a suggestion, only when the new mention says the work is still open, and then it says so: "Raised again on Oct 14 after it was closed on Sep 30."

The Tasks page

"Open tasks by customer, mined from meetings and emails. Most overdue first. Accept, assign, and close them right here."

• Two tabs: All tasks, the curated list, and Today, your queue for the day.
• Whose: All, Mine or My Team (you and the people who report to you in the org chart), plus a company list filter and By account, which groups tasks by customer.
• Toggles: Needs attention and External, each with its count.
• Search tasks…, New Task, Sweep All, Tasks Pulse, and a CSV download.
• Three sections: What we need to do, What they need to do and Suggested.
• On each row: the kind, owner and due date, an Overdue chip when it's late, the quote, where it was raised, and why it's in the list.

• A customer waiting on us never drops out of view, whatever its score.
• Suggestions age; accepted work doesn't. A suggestion leaves the list 21 days after it was last mentioned. A task someone accepted never ages out.
• A new task shows within minutes of the meeting or email that raised it.
• Every row opens. Any task link, from an email, a brief or the dashboard, opens the task. If it's no longer in the working list, one line says why, such as "Folded into another task", "Completed on (date)", "Snoozed until (date)", "Waiting on (who)" or "Last mentioned (date)", with the way back: open the task it was folded into, reopen it, keep it, accept it or unsnooze it.

The working list is the same everywhere: the Tasks page, the account rail, the dashboard, Today, the briefs and the reminders all read it, so the counts match.

Today

Today is the one place you act each day. It ranks everything you own across every account, sized to the time you have: "12 things today, about 50 minutes, at your pace of 20 a day."

• Sized to your day. Set one number, the actions a day you can do (20 by default): "You do 20 a day. Change this." Each kind of work has a time estimate (an email 2 minutes, LinkedIn 3, a call 5, a reply 5, a deal move 5, meeting prep 10), later learned from your own pace. Respond and Prepare always show; outreach fills what's left.
• Nothing is hidden to make the day fit. What doesn't fit moves to the next working day, with its due date, and never earlier than a snooze you set. An outreach step's spacing moves with it.
• Every card says why it's there, in one line: "They replied and are waiting on an answer", "Somebody is waiting on us", "A meeting is close", "This deal needs attention today", "The next step on this account is due", or "Nothing moves here until you do this one thing".
• Order inside a band: higher-priority accounts first, then deals further along, then whatever has waited longest.
• Only what's yours and ready: Today leaves out work you don't own, tasks with no date, hidden tasks, playbook checklists, which wait for the next call, tasks that look done, which wait for one confirm, and anything snoozed past today.

Start my day

Start my day opens a full-screen session, one card at a time, in band order, with outreach batched by channel (emails, then LinkedIn, then calls), since switching costs time. Each card shows "3 of 12 · Reach out", the account and its stage, the person and why now, what happened before, the time it should take and when it's due, and the draft or the call notes.

• Send (or Done, Enter), Skip (S), Another day (Z), Pause account and Close (Escape). Keyboard first.
• Log what happened after a call or LinkedIn step, with answers such as No answer, Left a voicemail, Talked — interested, Talked — not now, Meeting booked, Pointed me elsewhere or Asked not to be contacted. Each answer moves the pursuit, as an email reply would.
• "That is the day": the session ends with what's done, what was skipped or moved to another day, and the replies still waiting.

Driving work to closure

Most task tools stop at the list. Tasks keeps going until each item reaches an end state.

You close it

• Done.
• Dismiss, with a reason: "Why are you dismissing this?" Already done (counted as done), Not a task (that source learns not to raise it), Duplicate (merges into the task you pick) or Not mine (opens the reassign picker).
• Snooze until our next meeting with the account (it comes back the day before), tomorrow, next week or next month.
• Blocked: "What's blocking this?", so "in progress" never quietly means "stuck".
• Reassign to the right teammate.

Evidence closes it

ArcGlass uses proof it already has before spending anything new:

These closes apply to untouched suggestions. Every one records the quote and its source, and Reopen undoes it.

Looks done: for work a person owns

Evidence never closes a task someone accepted, edited or assigned. Instead, the card shows Looks done with the quote, its source and date, and asks: Yes, it's done or Not yet. A looks-done task leaves Today, leads the next Task Sweep as a one-keystroke card, and appears in the weekly reminder for one-click confirm. Not yet hides the prompt until new evidence arrives.

The engine closes it

Engine tasks close when their work is finished: an outreach step when it's sent or its pursuit ends, a prep task once the meeting has passed, a message action when its verdict stops firing, and a deal move when the move is cleared. Undoing a meeting handoff dismisses its prep task.

A drafted follow-up gets it out the door

Draft follow-up email on a meeting writes a customer-ready email from the meeting's bottom line and its open tasks. It's safe to send by construction: it covers agreed next steps and leaves out internal signals such as coaching notes and account health. Steer it ("warmer", "under four sentences"), regenerate it, then copy it into your own email and send it from there. Nothing is sent automatically.

What they need to do

When a customer owes us something, it sits in What they need to do, with what they promised and when. A nudge can be drafted for you to send; ArcGlass never sends it.

Task Sweep

Task Sweep clears a backlog by asking you to decide at most 7 things. Once your working list passes 15, the Tasks page says so, for example "18 to clear, about 2 minutes", with Sweep All.

"We'll read what happened after each open task and retire the ones the conversation already moved past. You decide the few that are still live."

1. Choose the scope: My tasks or My team, or sweep one account from its page. Include new, not-yet-organized tasks if you like, then Start sweeping.
2. ArcGlass reads the timeline for each open task: what happened on the account after it was raised. Untouched suggestions that a later commitment superseded, that the conversation moved past, or that duplicate another task are retired at once, reversibly.
3. You decide at most 7 cards. Tasks that look done come first, then anything a customer is waiting on, then the rest by kind of task, account and due date. Each card says why it's in the deck, for example "Customer waiting since Oct 3", and shows its evidence. Accept (Enter), Reassign (A), Already done (D), Drop (X), Snooze (S, 7 days) and Undo (←).
4. Tasks you accepted that look dead come to you as cards. ArcGlass never retires them on its own.
5. Nothing is left untouched. Suggestions past the 7 cards are parked until you next meet that account, or for 14 days. Accepted tasks stay on your list.
6. Check what was swept, grouped as "Superseded by a later commitment", "Expired — the conversation moved on" and "Merged as duplicates": "anything here can come back for 30 days."
7. Apply and finish. "Nothing is sent to anyone — assignments only." Then: "Sweep complete. You're clear."

A sweep is built to take under 3 minutes, even on a 200-task backlog. Every night, ArcGlass judges retirement candidates ahead of time, so a sweep opens fast. How long a suggestion is presumed live before age alone makes it a candidate depends on the account and the kind of task:

A suggestion also expires when three or more later conversations with the account pass without it coming up.

Tasks Pulse

Tasks Pulse, on the Tasks page, looks past single tasks: "A task is a symptom. A recurring class of task is a problem." It finds what keeps coming back across your conversations, such as the same document requested by account after account, and names What's missing. Pick a period (this week, the last 30 days or the last 90 days), Review one by one, and Accept a pattern to create a task to build what's missing, or mark it already done, drop it, reassign it, follow up or snooze it. Pulse needs at least 20 conversations in 90 days, and shows up to three patterns at a time.

Reminders and briefs

• The morning brief. At 7am local time on working days, the top of Today and the morning brief email say what the day holds, for example "14 actions, about 55 minutes. 2 replies first", with the top three items and a Start my day link.
• The weekly reminder. Every Wednesday, Managers and Organization Owners get one email written for them: their own tasks first, then unowned work, then the team, each with the customer, the deal, and the words that created it. Looks-done tasks are listed for one-click confirm. Nobody gets an empty reminder.
• Act from the email. Each task in an email has its own signed link. Opening it only shows the task, with Mark done and Snooze for 7 days; nothing changes until you press one, so a mail scanner opening the link can't complete anything. Links expire after three weeks.
• The post-meeting email includes a Suggested tasks section: the account's open tasks, with the ones from that meeting first, each linking into ArcGlass.
• The Monday weekly brief for Organization Owners lists up to 12 open tasks with their evidence.

You can mute the morning brief and the weekly reminder in your email settings, or from the link in the email.

Tasks and the rest of ArcGlass

Every engine's tasks stay in step with the engine, in both directions. Finishing a task in Today or Tasks finishes it in its source, and when the source finishes the work, the task closes.

A pursuit's last step is a question, not a chore: when the touch budget runs out, Done and Dismiss in the plain task list both mean "leave it open", the answer that loses nothing.

• Playbooks: a required step a conversation didn't cover adds a line to the account's "Ask on the next call" checklist, and a later call that covers it ticks the line.
• Email: a commitment made in a meeting and chased over email is one task with two mentions. In the email lanes, replies owed are tasks, and signal cards offer Create task.
• Meeting notes and Listen: a meeting's next steps are its tasks. Add one, or tick one off, in the notes or in ArcGlass Listen, and Tasks has it.

Where tasks show up

• Today and Start my day, for your day.
• The Tasks page: All tasks, Today, By account, and Tasks Pulse.
• Every account's Tasks tab: the account's open tasks from meetings, email and people, together.
• Every meeting: its next steps, with suggestions to accept or dismiss.
• The deal drawer in Engage: the deal's actions, and Add for a new one.
• The email lanes: replies owed and signal cards.
• The dashboard, for Managers and Organization Owners: My Tasks and Team Tasks, read from the same working list.
• Email: the morning brief, the weekly reminder, the post-meeting email and the weekly brief.

How it stays current

• Minutes after each meeting or email: new tasks are created, matched and judged, and evidence that closes tasks is applied.
• Every 4 hours: open tasks are judged again, duplicates fold, and suggestions the evidence settled are closed.
• Every night: duplicate suggestions merge, and Task Sweep's candidates are judged ahead of time.
• Every morning: Today is fitted to your number, and the morning brief goes out at 7am.
• Every Sunday: Messaging's weekly read creates the week's message actions.
• Every Wednesday: the weekly reminder.

Who can do what

• Tasks are shared, not private. There are no personal tasks: anyone in your workspace who can read conversations can see tasks and the quotes behind them, including internal work. Mine and My Team filter the list; they don't limit who can see a task. Today is personal: it shows only what you own.
• IT Admin, Billing and People roles don't have access to Tasks.

What it doesn't do

• It never closes or rewrites work a person owns without asking. It shows Looks done instead.
• It never deletes a task on its own. Merged and retired tasks are kept, with their history.
• It never sends a customer a follow-up or a nudge by itself. Those are drafts until a person sends them.
• It never makes a customer the owner of a task. What they owe us waits in What they need to do.
• It doesn't hide work to make a day fit. Work moves to the next working day, with its date.
• It doesn't sync tasks to Jira, Linear or your CRM. Tasks live in ArcGlass.

Frequently asked questions

Glossary

• Task: something our team owes, with an owner, a date and evidence.
• Suggested: a task ArcGlass proposed that nobody has accepted yet.
• Engine task: a task created by Pursuits, Engage, Messaging or an import, open from the start.
• Commitment, next step, follow-up, risk: the four kinds of conversation task.
• Evidence: the quote that raised a task, plus every later mention.
• Working list: the curated set each person sees, the same on every surface.
• What they need to do: what a customer or other party owes us.
• Looks done: evidence suggests an owned task is finished; one click confirms.
• Folded: same-objective tasks shown as one card.
• Today: your daily queue across every account, sized to your number.
• Task Sweep: a bounded, undoable review of at most 7 decisions.
• Tasks Pulse: recurring kinds of task, and what's missing behind them.

Related

• Task sweep: clear a backlog in a few minutes.
• Pulse: what keeps coming back.
• Draft follow-up: a customer-ready email from a meeting.
• Pursuits: outreach steps that land in Today.
• Engage: deal actions and meeting prep.
• Messaging: message actions in the Improve band.
• Conversation types: the playbooks behind the next-call checklists.