Help · FAQ
Answers to the questions we hear most.
Whether you are exploring Ridsys Platform, Ridsys Digital programs, or our resources, this page brings together the most common questions in one place.
Need something specific? Start here, then reach out to our team if you do not see your question covered.
Ridsys FAQ
Quick answers about platform, programs, and support.
General & getting started
How are Ridsys and Ridsys Digital different? ▾
Ridsys focuses on infrastructure—broadcasting headends, CAS, SMS/CRM, and subscriber experiences. Ridsys Digital delivers GrowthLab™ audits & experiments and Commerce Engine™ lifecycle programs to drive ongoing revenue.
Can I work with both divisions together? ▾
Yes. Many operators and brands deploy Ridsys infrastructure while engaging GrowthLab™ or Commerce Engine™ for growth. We build joint roadmaps so infrastructure data powers marketing experiments.
What industries do you support? ▾
Broadcasting, MSOs/LCOs, ISPs, hospitality and education networks tap Ridsys platforms. Consumer brands, B2B SaaS, and marketplaces rely on Ridsys Digital for growth programs.
How do I get support? ▾
Use the Support center for documentation and ticketing. Your division lead stays aligned with support so infrastructure fixes and experiment learnings flow into one shared plan.
Where can I find product docs and downloads? ▾
Support → Help Center → Downloads has manuals, firmware and app links.
How do I open a support ticket? ▾
Use the portal links (RSMS/RCRC) or the contact form, depending on SLA.
What are your support hours? ▾
Standard business hours, with 24×7 options on specific plans.
Do you provide remote support? ▾
Yes—L1/L2 remote help and on‑site assistance for AMC customers.
Where can I report a security issue? ▾
Use the security contact listed in the policy page.
Ridsys Platform & products
Broadcasting, CAS/DRM, SMS/CRM, and subscriber operations for MSOs, LCOs, and ISPs.
Can you integrate with our existing headend? ▾
In most cases, yes. We map entitlements, subscriber records and EPG to minimize cutover risk.
How long does deployment take? ▾
Typical PoC is 2–4 weeks; production rollouts vary by footprint and integrations.
Do you support IPTV/OTT as well as DVB? ▾
Yes—hybrid architectures with IPTV/OTT apps are supported.
What SLAs are available? ▾
Options include 24×7 incident response, uptime targets and spares coverage.
Is CAS compliant with content protection standards? ▾
R‑CAS includes pairing, entitlements and anti‑sharing features aligned to pay‑TV security practices.
Does R‑CAS support multi-operator setups? ▾
Yes—R‑CAS is built for multi-operator entitlements and flexible packaging.
How do you prevent piracy and credential sharing? ▾
Through STB/card pairing, real‑time entitlement checks and device-level policies.
Can it integrate with 3rd‑party SMS/CRM? ▾
Yes—via APIs; R‑SMS/R‑CRM integrations are native.
What reporting is available? ▾
Licenses, activations, deactivations, entitlement history and audit logs.
Is field upgrade supported? ▾
Yes—secure OTA mechanisms are available depending on STB family.
Does R‑SMS handle prepaid and postpaid? ▾
Yes—supports multiple billing models, reconciliations and dunning.
Do you have mobile apps for field teams or customers? ▾
Yes—native Android apps for collections and customer self‑service.
How are payments integrated? ▾
With R‑Pay and supported gateways; auto‑reminders and reconciliation included.
Can we export reports? ▾
Yes—CSV exports and APIs are available for BI tools.
What data privacy controls exist? ▾
Role-based access, audit logs and clear data retention policies.
Can technicians use the system on mobile? ▾
Yes—field apps support installations, tickets and SLAs.
Does it integrate with billing? ▾
R‑CRM integrates with R‑SMS/R‑Pay and can connect to 3rd‑party billing via API.
Can I build dashboards? ▾
Yes—operational dashboards with ticket SLAs, backlog and customer health.
Is there an API? ▾
Yes—documented REST endpoints are available.
How do you manage permissions? ▾
Role-based permissions with granular scopes.
Ridsys Digital, programs & resources
GrowthLab™, Commerce Engine™, and the content that supports audits, programs, and experiments.
What is GrowthLab™? ▾
GrowthLab™ is our experimentation program. We deliver audits, hypothesis backlogs, weekly experiment sprints, and clear learnings so teams know what actually drives growth.
How does Commerce Engine™ work? ▾
Commerce Engine™ combines Shopify builds, lifecycle automation (email/WhatsApp/SMS), and paid media management. We design the full commerce flywheel from acquisition to retention.
Do you collaborate with in-house teams? ▾
Yes. We slot into existing marketing, product, and revenue teams with shared KPIs, experiment reviews, and documentation that keeps everyone aligned.
What measurement foundation do you set up? ▾
Server-side tagging (sGTM), KPI trees, dashboards, and experiment logs ensure every campaign and journey reports back trustworthy data.
Which commerce platforms do you support? ▾
We support Shopify, Adobe Commerce (Magento), WooCommerce, BigCommerce, and custom headless storefronts — integrated with marketplaces and CRM/ERP systems.
How do you accelerate lifecycle marketing? ▾
We map journeys from onboarding to retention, build automations across email, WhatsApp, and SMS, and keep content fresh through experiment-driven creative testing.
Do you manage paid media as part of Commerce Engine™? ▾
Yes. Paid media is integrated with lifecycle and merchandising plans so budgets move in sync with product launches, campaigns, and cohort performance.
How do you measure success? ▾
Weekly KPI reviews across revenue, CAC, ROAS, retention, and repeat purchase rate. Dashboards highlight trends while experiment logs show what’s working.
Do you build or just optimize stores? ▾
Both—Shopify/Magento/Woo builds plus CRO retainers.
Will you manage marketplaces? ▾
Yes—Amazon/Flipkart catalog, ads and operations if needed.
How do you improve conversion rate? ▾
Hypothesis backlog, A/B tests, UX fixes and performance.
Do you fix slow pages? ▾
Yes—CWV improvements, image optimization and checkout cleanup.
How do you handle feeds? ▾
Clean product data, structured metadata and channel‑ready feeds.
Can you set up WhatsApp/SMS journeys? ▾
Yes—opt‑in capture, templates and lifecycle automations.
How do you ensure deliverability? ▾
Domain authentication, list hygiene and content/volume best practices.
Do you segment audiences? ▾
Yes—behavioral, RFM and lifecycle segments.
What's included in a measurement plan? ▾
KPI tree, events/params, consent and QA steps.
Do you support server‑side tagging? ▾
Yes—sGTM setup with enhanced conversion accuracy.
Which dashboards do you build? ▾
Looker Studio or Power BI with business‑level KPIs.
Do you run experiments? ▾
Yes—A/B test backlog, guardrails and analysis.
How do you validate tracking? ▾
Pre‑launch QA, compare sources and ongoing coverage checks.
Do you accept guest posts? ▾
Occasionally—pitches should be original, non‑promotional and practical.
How often do you publish? ▾
Aim for weekly; cadence may vary with product releases.
Can I request a topic? ▾
Yes—send suggestions via the contact form.
Do you anonymize clients if needed? ▾
Yes—upon request we can redact names while keeping metrics.
What metrics do you include? ▾
Baseline vs post results, timeframe and methodology.
Can we co‑publish a case study? ▾
Absolutely—co‑marketing opportunities are welcome.