Close

What Close can’t do on its own

Close is great for inside sales - calling, email sequences, and pipeline tracking for fast-moving teams. But between calls and stage changes, tasks pile up that Close can’t coordinate.

A rep logs a qualifying call. The coordination work starts immediately: someone needs to schedule a demo with a solutions engineer. Pricing needs approval. Legal has to review custom terms. Close records the deal, the calls and the emails, while each of those jobs needs someone outside sales to act.

What Close handles:

Built-in calling and SMS
Email sequences and tracking
Pipeline and deal management

What falls through:

Tasks between calls and meetings
Cross-team coordination for demos and proposals
Pricing exception approvals
Post-call follow-up assignments
Handoffs to Operations after close

How Tallyfy fills this gap

Tallyfy doesn’t connect to Close directly yet. A middleware tool such as Zapier watches Close for an event, like a logged call or a won deal, and launches the matching Tallyfy process with data from Close filled in. From then on, Tallyfy assigns each task, sets its deadline and tracks it.

Call follow-up workflows

When a call is logged in Close, middleware can launch a follow-up process. That process:

Assigns prep work to named people, or to a job title. A job title is filled when the process launches, so the middleware step that launches it has to say who fills it.
Tracks completion before the next touchpoint.
Escalates a task that runs late, once you add an expiring step and an automation for it. There’s no automatic escalation switch, so see escalating overdue tasks for the setup.

Demo and proposal coordination

Middleware can launch a demo or proposal process from a Close event, or a rep can launch one by hand. The process can:

Give a solutions engineer a task to schedule the demo.
Collect technical requirements in form fields on a task.
Split the proposal into one task per team that writes a part, each with its own deadline.
Put pricing and legal sign-off on approve/reject steps. An automation can send a rejected draft back for revision.

Post-sale workflows

When a deal is won in Close, middleware can launch an onboarding process with steps such as:

Handoff to Customer Success
Account setup and provisioning
Onboarding tasks, including ones the customer completes as a guest
Training scheduling

Connect today

Middleware: Connect via Zapier to trigger Tallyfy workflows from Close events. Tallyfy also has connectors for Make, Power Automate and n8n. The Close events you can start from are the triggers Close offers on the platform you pick. Launch via middleware walks through the setup.

API: Build a custom integration using Tallyfy’s API with Close’s REST API. Your code reads the Close event and launches the process through the API.

Webhooks: To send updates back the other way, use webhooks (messages Tallyfy posts to a web address you choose when an event happens, such as a completed task). Middleware or your own code can then update the Close record. See Tallyfy webhooks.

See also: Integrate to your CRM or ERP