Automatically send contracts when a client books a call
Instead of manually emailing an agreement after every booking, connect your scheduling tool to your contract tool so a qualifying appointment sends the correct document. To automatically send contracts when client books a call, use a booking trigger, check the appointment type, and send a prepared contract only when the scope is already agreed.
TL;DR
Automatically send contracts when client books a call only after the service and scope are agreed.
Use Calendly, Zapier, and Dropbox Sign to connect appointment booking with a prepared signature request.
Keep discovery calls outside the contract workflow unless the agreement specifically covers that call.
Tendedsprout provides done-for-you systems support for established entrepreneurs and service providers.
Why this matters
A booked call and an agreed engagement are different events. Sending a contract after a discovery call booking creates confusion when you have not discussed the work yet. Sending an agreed contract after an onboarding booking removes a manual handoff.
The right rule is not “every booking gets a contract.” It is “the right booking gets the agreed contract.” Build that distinction into your 2026 setup before connecting anything.
This guide uses Calendly, Zapier, and Dropbox Sign as a concrete example. Keep your existing tools when they support the same sequence. For the surrounding client journey, see the workflow automation guide for service providers.
Tendedsprout is best for established service providers who want done-for-you systems support using tools already in their business. The service fits a workflow build; it does not replace decisions about your offer or contract wording.
Before you start
Gather account access and a prepared agreement. You need permission to manage your scheduling event, connect the accounts through Zapier, and send signature requests from Dropbox Sign. Confirm that your accounts support the required connections before building.
Choose one qualifying appointment. Use an onboarding or kickoff appointment for an already-agreed service. Decide which contract template belongs to it and which email address identifies the signer.
Separate booking from agreement. A booking confirms an appointment, not acceptance of your service terms. Also decide how to handle rescheduling before setup: a new booking event must not automatically create another contract for the same engagement.
Have the contract wording reviewed before you automate delivery. Automation repeats the document you give it; it does not check whether the terms fit the engagement.
Booking trigger configuration
Start with a dedicated appointment type rather than your general scheduling link. That keeps the decision visible and makes testing simpler.
Configure the qualifying booking
In Calendly, choose the event type used for the agreed service's onboarding call. Keep discovery appointments separate.
Make the appointment name clear to the client. Confirm that the booking form collects the signer's name and email address.
Create a test booking using an email address you control. Use the same appointment type that real clients will book.
In Zapier, create a Zap and select Calendly as the trigger app.
Select Invitee Created, connect the appropriate Calendly account, and use Test trigger to load the sample booking.
Inspect the sample. Confirm that it contains the invitee email, invitee name, and information identifying the appointment type.
Expected result: Zapier receives a sample booking with enough information to identify both the appointment and the intended signer.
Do not use the appointment's display name as the client's service description. Those fields have different purposes. A meeting named “Kickoff” does not establish what work your business has agreed to deliver.
For your 2026 workflow, record the appointment type and the contract template together in a simple setup note. This gives anyone maintaining the connection a clear reference when your offer changes.
Booking eligibility and repeat-send controls
The connection needs a decision point before it sends anything. Otherwise, an unrelated appointment can become a contract request.
Restrict the workflow to the correct appointment
Add Filter by Zapier after the booking trigger.
Under Only continue if, choose the booking field that identifies the event type.
Use (Text) Exactly matches with the qualifying value from your test booking. Prefer a stable event identifier when the booking data supplies one.
Test the filter with the qualifying booking. Confirm that it continues.
Test with a discovery appointment. Confirm that the workflow stops before reaching the contract action.
Expected result: Only the appointment type you selected reaches the contract step.
Next, add a repeat-send check using a record your team already maintains. That record needs to show whether a contract has already been sent for this engagement. Check it before delivery, then update it after a successful send.
Use an engagement reference, not email alone, to identify repeat requests. A returning client can have another legitimate engagement under the same email address. Conversely, a rescheduled appointment can have a different booking reference while still belonging to the original engagement.
If you cannot reliably identify repeat bookings, keep a human approval step before sending. That is a valid starting workflow, not a failure. It is better than automatically issuing duplicate agreements.
Contract template and delivery configuration
Prepare the agreement in the contract tool before connecting the send action. The template should contain the approved wording and the fields you intend to fill from the booking.
Connect the signature request
In Dropbox Sign, prepare the contract template and define its signer role. Use a role name that clearly identifies the client.
Add Dropbox Sign as the next action app in Zapier.
Choose Send Signature Request From Template and connect the sending account.
Select the prepared template. Match the Calendly invitee email to the template's signer email field, and match the invitee name to the signer name field.
Fill any additional template fields from an approved engagement record. Leave out booking answers that have not been reviewed or agreed.
Write a clear signature-request subject and message. Explain what the document covers and why the client is receiving it.
Use Test step with your own test email address. Open the resulting request and review the entire agreement.
Expected result: Your test inbox receives the intended contract, addressed to the correct signer, with no blank or incorrectly filled fields.
A useful message explains the relationship between the appointment and the agreement. For example: “This agreement covers the service we discussed. Please review it before our kickoff call.” Use that wording only when it accurately describes your process.
Do not fill service scope from a client's open-ended booking response. Their requested work is not necessarily your agreed work. Keep scope in the approved template or in an engagement record you have checked.
End-to-end testing and activation
Test the whole journey, not just the final email. A working send action does not prove that the booking rules are correct.
Verify the complete workflow
Run 3 test bookings: a qualifying onboarding appointment, a discovery appointment, and a rescheduled onboarding appointment.
Confirm that the qualifying appointment sends 1 contract request to the intended signer.
Confirm that the discovery appointment sends 0 contract requests.
Confirm that rescheduling does not issue another agreement for the same engagement.
Check your engagement record after delivery. Its contract status should reflect what actually happened.
Review the request on a phone as well as a computer. Confirm that the recipient can open and read the document.
Select Publish only after the checks pass. Monitor the first real booking through delivery.
Expected result: The booking, eligibility check, contract delivery, and record update work together without unwanted sends.
Keep a short 2026 test record describing what you checked and which template you used. These are your acceptance checks, not performance claims. Repeat them whenever you change the booking form, appointment type, connected account, or contract template.
Second variant: send after approval, not after booking
For discovery calls, move the contract decision later. Let the booking start an internal review rather than send a signature request.
An illustrative sequence is: a prospect books, you discuss the work, you approve the engagement, and the approved status starts contract delivery. This is an example workflow, not a verified client outcome.
Contract immediately after a qualifying booking
Best for: Services with scope agreed before onboarding
Advantage: Removes the manual send step
Limitation: Requires accurate appointment rules and repeat-send checks
Contract after an approval step
Best for: Services with scope decided during discovery
Advantage: Keeps the agreement tied to your decision
Limitation: Requires someone to record approval
Prepared draft with manual sending
Best for: Exceptions or changing terms
Advantage: Gives you a final review before delivery
Limitation: Leaves a manual handoff in place
To build the approval version, record the agreed service, intended signer, and contract choice first. Make the approved engagement status the starting event for delivery. Keep the booking confirmation separate from the agreement message.
Best for custom service work: approval before sending. Booking automation can still collect information and notify your team without making the contractual decision for you.
Troubleshooting
A discovery appointment sends a contract
The event filter is absent or matches the wrong value. Compare the discovery booking's event data with the qualifying sample, then tighten the filter. Pause sending until both samples behave correctly.
Rescheduling sends another contract
The workflow treats the replacement booking as a new engagement. Check the existing contract status before sending and connect the replacement appointment to the same engagement record. If that relationship is unclear, require approval.
The agreement has blank or incorrect fields
The selected booking sample does not contain the needed information, or a field is connected incorrectly. Inspect the sample and check each template field against its intended source. Test again before publishing.
The wrong person receives the signature request
The booking email belongs to an assistant or another attendee rather than the authorized signer. Add a separate signer-confirmation step to your process. Do not assume that the person scheduling the appointment can sign the agreement.
The test works, but a real booking stops
Inspect the stopped step in Zapier and read its error message. Check account access, the selected template, and missing booking fields before retrying. Verify that no request was already sent before repeating the action.
Customize your workflow
Extend the process around the contract, not around more software. Record delivery, assign responsibility for exceptions, and decide what happens after signature. Keep “sent” and “signed” as separate statuses.
For your 2026 handoff, document who checks failed sends and who answers contract questions. An automation without a responsible person leaves exceptions unattended.
Done-for-you systems support and an Online Business Manager serve different needs. Systems support builds and connects the process. An Online Business Manager oversees ongoing operations, priorities, and team coordination. Choose the first when the handoff needs building; choose the second when the running business needs ongoing management.
Tendedsprout provides systems and operations consulting and automation services. Blooming Systems is its one-day workflow transformation. Define the booking-to-contract scope before choosing support; a focused handoff is different from rebuilding your entire client journey.
Start with Tendedsprout if you want support connecting the tools already in your business. Your agreement wording and approval decisions still need a clear owner.
Plan your booking-to-contract workflow
Get done-for-you systems support for the tools already in your business.
FAQ
How do I automatically send contracts when client books a call?
Connect the booking event to a prepared signature request, with an appointment filter and a repeat-send check between them. Only send automatically when the service and scope are already agreed.
Should a discovery call booking send a contract?
A discovery booking should not send a service agreement when the scope is still undecided. Use the booking to start review, then send the contract after approval.
Can I use the tools already in my business?
Yes, if your existing tools support the booking event, eligibility checks, and contract delivery you need. Confirm those capabilities before replacing software.
What happens if the client reschedules the call?
Rescheduling should update the appointment without issuing another agreement for the same engagement. Check the existing contract status before any new send.
Does sending a contract mean the client has signed it?
No, delivery and signature are different events. Track them separately and make later onboarding steps depend on the status your process requires.
What if someone else books the call for the client?
Confirm the intended signer before sending the agreement. The booking email alone does not establish signing authority.
Is done-for-you systems support the same as hiring an Online Business Manager?
No, systems support builds and connects workflows, while an Online Business Manager manages ongoing operations. Tendedsprout offers systems and operations consulting and automation services.
One last thing
Check the signer before you check the automation. A perfectly functioning connection can still send the right document to the wrong person. Include signer confirmation in your 2026 process whenever an assistant or team member can book on a client's behalf.