Skip to content
NewSee how
New

Schedule activities and never miss a follow-up

Schedule calls, tasks, meetings, emails, and deadlines against any contact or deal, assign them to a teammate, and get an automatic reminder email when one comes due.

Published
Reading time
2 min read

The deals you lose are rarely the ones you got wrong. They're the ones you forgot to follow up on: the call you meant to make Thursday, the proposal you were going to chase next week. Scheduled activities give every contact and every deal a to-do list with due dates and automatic reminders, so following up stops depending on your memory.

What changed

You can now schedule an activity against a contact or a deal and give it a type: a call, a task, a meeting, an email, or a deadline, with a due date picked from a proper date picker. Assign it to yourself or a teammate (only workspace members can be assigned), and it shows up on that contact's or deal's Activities panel.

The panel keeps you honest with four filter tabs: Upcoming, Overdue, Done, and All. Anything past its due date gets an Overdue badge so it can't hide. Tick an activity Done when you've handled it. Reopen it and its reminder re-arms.

The reminder is the part that does the real work. When an activity comes due, the assigned teammate gets a reminder email on its own, with no separate reminder app and no calendar juggling. Reschedule an activity by changing its due date and the reminder re-arms for the new time. Scheduled activities also land on the Contact 360 and Deal 360 timelines, so a follow-up you planned sits in the same history as the calls and emails it follows.

How to use it

  1. Open a contact (from Contacts) or a deal, and go to its Activities panel.
  2. Add an activity, choose its type (call, task, meeting, email, or deadline), pick a due date, and assign a teammate.
  3. Save. It appears under Upcoming. If its due date passes, it moves to Overdue with a badge.
  4. When it comes due, the assignee gets a reminder email.
  5. Mark it Done when it's handled. Need to push it? Change the due date and the reminder re-arms.

Why it matters

Follow-up discipline is what separates a pipeline that closes from one that leaks, and discipline is exactly the thing that breaks down when you're busy. Scheduling an activity and letting the system remind you moves the remembering off you. You decide once, when the context is fresh, that you'll call this person Thursday, and Thursday the reminder finds you, instead of the follow-up quietly aging out of your attention.

Because the activities live on the contact and deal themselves, they also double as a record. Anyone looking at the deal can see what's planned next, not just what's already happened, so a teammate covering for you, or a manager checking on a deal, knows what the next move is without asking. Follow-ups planned here show up right on the Contact 360 and Deal 360 timeline, inside the Companies and Deals CRM.

All updates

Outreach that keeps going after you log off.Leads, emails, follow-ups and replies, handled.

Connect unlimited mailboxes and let AI agents find leads, write each email and follow up. Or send your own templates in manual mode. From $29/mo.

Start your $1 trial See pricing

$1 for 3 days · Cancel anytime · No contract

Install with AI

Your coding agent sets up the FirstSales CLI and skills for you.

Prompt for Claude Code

I'm setting up FirstSales (https://firstsales.io), an AI outbound sales platform: campaigns, contacts, a reply inbox, deliverability and lead signals. Help me get my workspace sending real, good emails end to end, from Claude Code.

Read these first so you know how FirstSales works:
- Developer docs and API: https://developer.firstsales.io
- CLI: https://www.npmjs.com/package/@firstsales.io/cli
- Skills for coding agents: https://github.com/firstsalesio/firstsales-skills (read README.md and GUIDE.md)

Setup
1. Install the CLI: npm install -g @firstsales.io/cli
2. Install the FirstSales skills:
   claude plugin marketplace add firstsalesio/firstsales-skills
   claude plugin install firstsales@firstsales
3. Ask me if I already have a FirstSales account. If not, send me to https://app.firstsales.io to sign up.
4. Ask me to create an API key under Settings → API → API Keys, with only the scopes we need.
   Never ask me to paste the key into this chat. Tell me to run this in my own terminal, so the key stays hidden:
   read -rs FS_KEY && firstsales auth login --api-key "$FS_KEY"; unset FS_KEY
5. Run `firstsales whoami` and tell me which workspace and organisation we are connected to.

Then ask me about my business: what I sell, who I sell to (roles, company size, countries), my best customers, and what I use today for outbound (tools, lists, mailboxes). Walk me through:
1. Teaching FirstSales my business: website, offer, proof points and case studies in the knowledge base, so the AI writes like someone who knows the product.
2. Connecting my sending mailboxes and checking my sending domain: SPF, DKIM, DMARC and warm-up. If anything is unhealthy, tell me the exact DNS record to add.
3. Bringing in contacts: import my CSV or CRM export into a clean list, remove duplicates and bad emails, and block domains I must never email (customers, competitors, my own).
4. Building my first campaign: the right list, senders, steps and timing. Write the sequence with me, show me the drafts, and do not launch until I say yes.
5. Setting up Signals if it fits: find people engaging with LinkedIn posts about topics my buyers care about, and turn them into leads.
6. Inviting my team and giving each person the right access.

Once campaigns run, show me how to work the reply inbox from here: which replies need an answer, draft responses in my voice, and move good conversations into deals. If I use Cal.com, connect it so follow-ups can offer my booking link (not the first email).

Throughout, as you learn about my business, proactively suggest and help create:
- Reply templates for the questions and objections my prospects are likely to raise, based on my product, site and codebase if you can see them.
- Campaign ideas and segments worth testing, with the reason for each.

Safety rules:
- Show every change as a dry run (--dry-run) first and wait for my yes. Never send emails, launch campaigns or delete anything without my yes.
- Tell me before anything that spends credits, and how many.

Be opinionated. If the docs give a sensible default, just use it. Don't make me choose between five options.
Developer docs ↗npm: @firstsales.io/cli ↗GitHub: firstsales-skills ↗