Project scope
Markets, use cases, message types, access paths, delivery milestones and support are defined in the business documents agreed by both parties.
Terms of service
Shared rules for operable enterprise messaging
These terms apply to the Notify2You website and enterprise RCS aggregation, messaging operations, API integration and SMS fallback services.
01 / Scope
Service scope and collaboration
Notify2You provides enterprise RCS Business Messaging aggregation, carrier and channel coordination, rich-message orchestration, API integration and SMS fallback services.
Enterprise responsibilities
The enterprise manages sender information, message content, recipient consent, business instructions and connected systems.
Service collaboration
Notify2You coordinates access, orchestration, routing collaboration, status events and operations support under the agreed solution.
02 / Responsible use
Content, consent and purpose
Manage appropriate consent
Record the relevant consent source, purpose, frequency and opt-out path before sending.
Keep content accurate
Maintain valid brand, copy, media, links, suggested actions and related permissions.
Protect integration credentials
Apply appropriate controls to API keys, webhook signatures, access permissions and related business data.
Maintain operational response
Address recipient feedback, opt-outs, abnormal events and service changes promptly.
03 / Delivery conditions
Message delivery is a coordinated path
RCS availability and delivery outcomes depend on target market, carrier, sender, device, network state, recipient settings and business rules.
Notify2You organizes channel coordination, status handling and SMS fallback around those conditions to help enterprises maintain observable, operable notification journeys.
Business documents
Pricing, billing units, payment arrangements, service term, support level and project change processes are governed by the business documents agreed by both parties.
Plan a service solution ↗Clear collaboration
Make the use case, responsibilities and delivery path clear.
Start with one priority RCS notification and coordinate content, engineering, operations and governance.