Operating Legal Framework

Terms of Service

Last Structural Revision: July 2026 // Global Telephony Architecture Binding

Welcome to RCMContact. These Terms of Service ("Terms") govern your deployment, access, and usage of the cloud contact center software platforms, automated dialing APIs, predictive algorithms, and smart interactive voice response (IVR) architectures managed by RCMContact ("we," "us," or "our").

By provisioning an account, accessing our sandbox dashboards, or initializing voice connectivity lines, your enterprise organization ("Client," "User") agrees to be bound by these Terms. If you do not accept these governance terms, you are prohibited from utilizing our service modules.

1. Workspace Provisioning & Authorized Platform Use

Clients are granted a limited, non-exclusive, non-transferable, revocable subscription to run our enterprise communications workspace. All account users must maintain secure credentials, and the Client remains fully accountable for all voice call payloads, SMS distributions, and API transaction queries initiated through their production tenant dashboards.

2. Strict Compliance with Telecommunication Laws

RCMContact functions exclusively as a high-velocity carrier transmission utility. The Client retains 100% legal accountability for coordinating the regulatory alignment of their outreach campaigns. Use of our automated dialers must strictly abide by all regional laws, including:

United States: FCC Telephone Consumer Protection Act (TCPA) compliance rules, national Do Not Call registries, and specific state wiretapping laws.
India: Telecom Regulatory Authority of India (TRAI) frameworks governing transactional commercial communication lines and BPO registration constraints.
Data Privacy: Strict validation of consumer or patient opt-in logging data before initiating outbound voicemail loops or messaging batches.

Prohibited Campaign Restrictions: Outbound dialing campaigns containing fraudulent financial metrics, unverified medical collection assertions, or missing opt-in verification structures will trigger instant workspace suspension without liability or refund recourse.

3. Cross-Border & Offshore Operations Safe Harbor (BPO/KPO Logistics)

For clients utilizing our system architecture across distributed offshore call delivery channels (including but not limited to Indian BPO nodes dialing into US/UK healthcare networks), the Client assumes full cross-border legal ownership. RCMContact does not manage local offshore employee conduct or staffing operations. It is the Client's absolute responsibility to enforce strict multi-jurisdictional data perimeter insulation rules and maintain local workforce telecom connectivity licensing agreements as required under TRAI or international data transit protocols.

4. Automated Call Recording Consent & CTI Warning Obligations

Our communication consoles provide built-in voice logging, dual-channel CTI call recording, and automated transcription capabilities. While RCMContact incorporates security filters and compliance-friendly redaction features, the Client bears the sole responsibility for ensuring proper legal consent notification parameters are met on every live voice path. If your operations cross into single or two-party notification states, you must configure your interactive IVR streams or agent script playbooks to announce call recording instances accurately.

5. Telephony Rates, Billing Structures & Overages

Platform accessibility is billed according to your designated Master Service Agreement subscription level. Carrier network connections, inbound/outbound voice minutes, toll-free number leasing, and SMS payloads are tracked via system monitors and processed on a monthly cycle. Any additional volume or overages calculated outside your baseline contract scale will be billed instantly at standard variable transit rates.

6. Platform Uptime Commitments & Maintenance Windows

We aim to provide a 99.9% network uptime percentage for our cloud voice nodes, excluding scheduled technical maintenance routines. Maintenance structural updates are typically executed during low-traffic operational windows (12:00 AM to 4:00 AM EST) and communicated via system status boards. We assume no structural liability for downtime instances stemming from carrier routing blockages, local internet service failures, or client-side API configuration errors.

7. Intellectual Property Insulation

The unique coding architecture, UI layouts, underlying source structures, predictive sorting algorithms, NLP audio redaction scripts, and platform assets belonging to RCMContact remain our exclusive intellectual property. Clients are expressly prohibited from reverse-engineering, duplication vectors, or scraping internal codebase systems.

8. Limitation of Liability & Indemnification

In no scenario shall RCMContact be liable for consequential losses, lost profits, missing operational data, or carrier blocking liabilities stemming from campaign configurations. The Client agrees to fully defend, indemnify, and hold harmless RCMContact against any claims, financial fines, or legal penalties resulting from compliance violations, unauthorized telemarketing execution, or missing consumer consent parameters on the Client's part.

9. Termination Procedures

Either party can dissolve the active communication workspace configuration by filing a formal cancellation notice thirty (30) days prior to the next billing lock date. Upon system termination, access to the master API keys and staging panels will be permanently turned off, and all trailing usage overages will become due instantly.