Afterping · Legal document
Draft – Pending Legal Review
Terms of Service
Afterping is an online lead-recovery product for HVAC and plumbing contractors. This draft is organized for review and does not establish final contractual terms.
Bracketed owner and counsel notes are unresolved placeholders. Confirm them before publishing a final document.
1. Document details
[OWNER INPUT: Insert the provider’s full legal name, entity type, formation jurisdiction, principal business address, and the effective date approved for the final terms. Confirm the product name and contracting entity are correct.]
2. Parties and acceptance
The final agreement should identify the provider and the contractor or other business customer that accepts it. It should state which account users may accept or act for a customer and the event that forms the agreement.
[COUNSEL INPUT: Specify the acceptance method, authority required, contracting party for each account, and any order form or supplemental terms that apply.]
3. Service description
Afterping’s website describes lead-recovery workflows for missed service calls, aging estimates, and canceled appointments, with a focus on HVAC and plumbing contractors. The checked-in application includes an admin-facing lead inbox and lead records, recovery status and activity history, editable SMS and voice message templates, and a consent-aware audience preview.
The audience preview applies filters and returns a count. The inspected application routes do not send or queue messages. The website also advertises AI voice and SMS recovery, but the inspected application code does not establish that those delivery or AI capabilities are implemented or enabled in production.
[OWNER INPUT: Confirm the production service scope, enabled channels, integrations, supported workflows, and any service limits before describing them as included features.]
4. Accounts and permitted use
The application includes email-and-password account registration, email verification, and role-based access to its administrative lead and template tools. The final agreement needs to state account eligibility, user administration, credential responsibilities, acceptable use rules, and any restrictions on access or use.
[COUNSEL INPUT: Add the approved account, access, prohibited-use, and suspension rules. Do not treat this draft as setting those rules.]
5. Customer responsibilities
The application has fields for contractor-entered lead names and contact details, lead source and type, consent and opt-out state, recovery status, notes, follow-up timing, booking outcome, activity history, and message templates.
[COUNSEL INPUT: Define customer duties concerning authority to provide lead data, its accuracy and permitted use, customer notices and permissions, user access, and compliance with laws that apply to the customer’s communications and services. Confirm the allocation of responsibility for consent and opt-out records.]
6. Messaging, automated tools, and integrations
The current site copy refers to AI voice and SMS. The inspected app stores SMS and voice templates and supports a count-only audience preview; it does not show an operation that transmits or queues a message. This code review does not determine whether separate production systems or integrations are used.
[OWNER INPUT: Confirm whether production sends SMS or voice calls, uses AI or human review, records calls, connects to third-party systems, or processes delivery results. Counsel should define the parties’ duties and any channel-specific terms only after that scope is verified.]
7. Fees, taxes, and payment
[OWNER INPUT: Provide the actual offer, prices, billing basis, currency, taxes, invoice timing, payment method, renewal terms, failed-payment handling, and any trial, refund, or cancellation terms. Confirm whether fees apply before including this section in a final agreement.]
8. Customer content and rights
Customers may enter lead records and create or edit message templates in the application.
[COUNSEL INPUT: State each party’s rights in customer data, templates, and other materials; any limited service-use license; and rules for feedback, export, and deletion. Do not infer these rights from the application fields.]
9. Availability, support, and changes
[OWNER INPUT: Describe support channels and hours, planned maintenance, availability commitments, service levels, support response targets, integrations, and change notice practices if any are offered. No such commitment is established by the inspected application.]
10. Suspension, termination, and cancellation
[COUNSEL INPUT: Set the permitted grounds and process for suspension or termination, customer cancellation method and timing, treatment of prepaid fees, access to or export of records, and post-termination deletion or retention.]
11. Warranties and disclaimers
[COUNSEL INPUT: Draft any express service commitments and legally appropriate warranty disclaimers. Do not add an uptime, recovery-result, compliance, or uninterrupted-service promise unless the owner approves the commitment and can support it.]
12. Limitation of liability
[COUNSEL INPUT: Define any liability limits, exclusions, exceptions, caps, and applicable time periods after reviewing the parties, service, data, and governing law. No limit is supplied in this draft.]
13. Indemnity
[COUNSEL INPUT: Decide whether either party will indemnify the other, identify covered claims and procedures, and specify any exclusions or limits. No indemnity obligation is supplied in this draft.]
14. Confidentiality and security
[OWNER AND COUNSEL INPUT: Confirm whether separate confidentiality terms apply and identify only security and incident-response commitments that have been verified and approved for disclosure. This draft makes no security or confidentiality promise.]
15. Governing law and disputes
[COUNSEL INPUT: Select the governing law, courts or dispute-resolution process, venue, and any required notice, escalation, or arbitration terms. Do not infer a jurisdiction from the intended customer market.]
16. Notices and other terms
[OWNER AND COUNSEL INPUT: Provide the provider’s formal notice address and permitted notice methods, and add any approved assignment, force majeure, entire-agreement, amendment, severability, waiver, and order-of-precedence terms. Confirm whether notices may be sent electronically.]