In-house SDR team vs Alba: cost both, side by side.

Commercial scope

Put the exact configuration and governing documents in one written order record.

• Seat count Owner: Joint Record whether the order covers three, four or five caller seats and whether seats launch together or in phases.
• Caller and data tiers Owner: Joint Identify standard or experienced callers, Budget or Premium data, and every optional product line.
• Billing and order documents Owner: Joint Confirm recurring cadence, setup fee, billing date, taxes, Order Confirmation, Services Agreement and any addendum.
• Included work and exclusions Owner: Joint List the channels, markets, hours, handoff tasks and anything that is outside the engagement.

Roles and launch dependencies

A launch date is confirmed in writing after the inputs below are settled. This checklist does not create a blanket launch time.

• Named owners Owner: Joint Name the Alba delivery owner and the customer owner with authority to approve scope, data, script and changes.
• Offer and claims Owner: Customer Customer confirms the offer, commercial terms and substantiation for every claim callers may make.
• Written ICP and exclusions Owner: Customer Customer approves target criteria, disqualifiers, named-account exclusions and territory rules.
• Approved script Owner: Joint Alba develops the script and the customer approves the final version in writing before use.
• Data source and contact rules Owner: Joint Identify the source, the party responsible for lawful use, and any required registry scrub before records are transferred or dialled.
• Suppression instructions Owner: Joint Customer supplies current written do-not-call, suppression and consent instructions. Alba confirms in writing when an instruction has been applied; no fixed turnaround is implied here.
• Calendar, CRM and handoff Owner: Joint Confirm systems, access, field mapping, qualification criteria, meeting owner and routing test.
• Written campaign launch date Owner: Joint Record the date only after the agreed dependencies are complete, including who can move it and how a change is documented.

Reporting and quality review

The published agreement defines weekly activity reporting. The engagement still needs a written quality-review method.

• Weekly report fields Owner: Alba Confirm dials, connects, conversations and meetings booked, plus the source system and reporting owner.
• Shared definitions Owner: Joint Define dispositions, connects, conversations, qualification and meeting handoff so both teams read the report the same way.
• Recording decision Owner: Joint Confirm whether recording is enabled, the required notice or consent allocation, access and retention.
• Quality-review sample Owner: Joint Agree the number or selection method for calls reviewed, review frequency and evidence retained. No default sample or cadence is promised here.
• Quality scorecard Owner: Joint Agree the fields to inspect, such as script adherence, claim accuracy, discovery, qualification evidence and disposition accuracy.
• Feedback and escalation Owner: Joint Name who reviews findings, who can approve a script or ICP change, and how unresolved issues are escalated.

Continuity and backfill

Continuity terms are not inferred from the number of seats. Put each operational decision in the Order Confirmation or addendum.

• Absence coverage Owner: Joint Agree what happens to scheduled service, reporting and billing during planned or unplanned caller absence.
• Backfill trigger and approval Owner: Joint Define when a replacement search begins, who approves a proposed caller and what evidence accompanies that decision.
• Backfill timing Owner: Joint If a target timeline is required, write it into the order. This page does not promise an automatic replacement or a fixed replacement time.
• Handover and access changes Owner: Alba Record script, account context and open work before access is removed from one caller and granted to another.
• Commercial treatment Owner: Joint Agree how unavailable service days, a phased start or a backfill period affect delivery and billing.

Cancellation, ownership, data and security

The signed documents control. Review the public documents, then record engagement-specific requirements and limitations.

• Cancellation and renewal Owner: Joint The published Services Agreement describes notice before the next billing date and service through the current prepaid period. Review the selected billing period, end date, setup-fee treatment and refund position in the signed documents.
• Data ownership and return Owner: Joint The published Services Agreement assigns customer data, approved scripts and customer deliverables to the customer. Confirm the required export format, access handoff, retention and deletion instructions.
• Systems and processing locations Owner: Joint Identify every system, sub-processor, personnel location and international-transfer document that applies before personal data is transferred.
• Security controls and evidence Owner: Joint Request the controls and evidence your review requires. The public DPA is not a security certification, and unavailable controls must be identified in writing before processing.
• Access and offboarding Owner: Joint Define account ownership, authentication, logging where available, least-required access, review points and removal at end of need.
• Incident contacts and process Owner: Joint Name both incident contacts and review the notification, cooperation and audit provisions in the signed DPA.
• Customer legal review Owner: Customer Customer confirms its own counsel has reviewed the markets, lists, scripts, recording choices and outreach instructions where required.

Read the source, then record engagement-specific terms.

This checklist is a planning aid, not a contract, legal opinion, security certification, launch commitment, replacement commitment or outcome forecast. The signed Order Confirmation, Services Agreement, DPA and any addendum govern the engagement.