Perplexity Teammates Own Recurring Jobs Week After Week

The support queue refills overnight. The pipeline goes stale by Friday. The bug list grows while everyone is busy with louder work.

None of that work is hard in a single pass. It fails in the repeat, because nobody owns the tenth pass as carefully as the first. Perplexity Teammates is built for that gap. You give one agent one job, and that job stays assigned until you change it.

A job, not a prompt

Most agent tools start from a prompt. Teammates starts from a job description, and the help center gives that description four parts. Getting those four parts right is most of the setup work, and it is work a person has to do with care.

The examples in the help center show the shape at its best. Watch one alerts channel and reply to each bug report with a likely cause and a suggested fix. Watch Linear for updates in your areas and send a weekly summary, with stale projects flagged. File action items in Linear from the feedback posted in one product channel.

Read those examples for what they share. Each one names a single source, a single kind of output and a clear moment to act. A role written as own everything about support has none of that. The tool rewards narrow writing about work, which is a polite way of saying it punishes vague management.

How the job runs between reviews

Once the role is set, a teammate plans the work on its own. For a large goal, the help center says it breaks the goal into tasks, works out which tasks can run at the same time, and starts more agents for those tasks. Each added agent gets its own computer and works on its task from start to finish.

The teammate then collects the results and checks them before it decides the next steps. It can add agents as a project grows and redirect them when new information arrives. Finished work comes back for your review as a report, a pull request or a change to a configuration, in the examples Perplexity gives.

Watching is the part that makes the job recurring rather than merely repeated. A teammate monitors the tools you connect and can start work when something arrives, then follow up on that work. Perplexity gives the example of a teammate that opens a pull request and later responds to review comments on it.

Memory closes the loop. Feedback you give in the chat of a teammate applies to later work, per the help center. The launch post gives a plain example. Tell an operations teammate that an agency needs two weeks of notice, and it counts that lead time in later schedules. That claim is a company example, not a measured result, and it is still the right first thing to test with a small job of your own.

The recurring shape in one picture: the same kinds of work arrive again, and the value sits in how each pass is handled. Illustration: Dirty Static

That shape also explains the link to our research review of Teammates, which weighed the launch as a product to buy. This profile asks a narrower question. If you already have Max, what job would you actually hand over, and how would you write that job down?

Jobs that fit the shape

The launch post walks through four areas of a business, and its examples are useful as a test of fit. In sales, a teammate notices when a regular customer stops buying, reviews order history and support issues, and drafts an offer or flags a problem to fix first. In support, a teammate reviews the complaints from the day before, sums up trends, flags cases that need a personal reply and drafts those replies.

In operations, a teammate tracks deadlines and missing items and follows up when a deadline is 72 hours away. In marketing, a teammate watches campaign results and rival promotions, drafts fixes when results slip and suggests responses when a rival changes prices. All four are company examples, and all four share the same traits. The work arrives on a rhythm, the sources are named, and a person still reviews the outward step.

Jobs that lack those traits fit badly. Work that needs taste calls on new facts each time, work with no stable source, and work where a wrong outward step costs real money or trust should stay with a person, or stay behind strict approval until a teammate has earned trust on safer ground. Our Claude in Chrome and Cowork review reached a similar line for Anthropic tools. The value sits in routine work inside signed in tools, and the risk sits in the same place.

What it costs

Max is the entry ticket, and credits are the meter inside it. Prices below were checked on November 8, 2026 against Perplexity plan reporting that cites the Max plan pages, and they match the figures in our research review.

Perplexity has published no typical cost for one teammate doing one real job for one month, and no limit on how many teammates one account may create, in the sources checked for this profile. That gap matters more than the headline price. A single daily summary and a teammate that spawns parallel agents on a large codebase are both Teammates use, and they will not cost the same.

Which should you choose

Choose Teammates if you hold Max and own one recurring job with a named source and a named output. Start with the morning support summary, the weekly pipeline review or the bug triage pass. Write the role with the four parts in the table above, keep approval on, and judge the first month on three counts. Work delivered right, times you had to step in, and credits burned.

Choose Teammates with more than one role only after the first role earns it. Teammates in the same Project share files, goals and instructions, and they can pass work to each other, per Perplexity. That is a strong second step. It is a poor first step, because two vague roles are harder to audit than one clear role.

Look elsewhere if you are on Free or Pro and the job is small. A tenfold plan jump needs a job that is worth $200 a month on its own. Look elsewhere, too, if your work needs Enterprise controls today, since Enterprise accounts are not included by default in this preview, or if the work has no rhythm. A task you do once belongs in Computer as a single project, not in a standing role.

Final thoughts

Teammates is best read as a new form to fill in, not as a new colleague to meet. The form asks for a source, an output, a schedule and an audience, and the quality of the work will track the quality of those answers more than any claim about models.

That is a healthy shape for a tool in The Arsenal. It makes the buyer do the clear thinking first, and it gives the buyer a thread, a desktop and a usage page to check what happened next. Hand it one recurring job, written down with care, and let a month of reviewed work decide whether a second job follows.

Sources

• Launch post, ongoing ownership, monitoring, business examples and setup: Teammates are agents for complex, ongoing work, Perplexity
• Help center, capabilities, setup, role parts, orchestration, credits, models and security: Get started with Perplexity teammates, Perplexity Help Center
• Screenshot: Perplexity Help Center, credited at the image. Hero and body illustrations: generated by Dirty Static, in the house style.