rWeb is the digital experience layer: public websites and content, authenticated client portals and branded mobile apps, connected to the systems behind them.
Websites, content management, multi-site and multilingual structures, landing pages and SEO.
Customer areas with authentication, account interfaces, documents, notifications and security.
Branded mobile experiences combining customer areas, payments, notifications and support.
A broker needs a multilingual public site, a client area and a mobile app.
The site launches first; the client portal adds authentication, documents and notifications; the branded app follows once the app-store accounts are in place. All three use the same content and the same account integrations; support inside them runs on rAgent where that product is included.
One platform to maintain, one experience for the client across public and authenticated surfaces.
Your back-office systems through API; rAgent, rPlatform or rPAM where those surfaces are in scope.
rWeb takes content and account data in and puts websites, portals and apps out. The web pillar stands alone; portal and app need the account systems and, for publishing, your own app-store accounts.
Support and assistance inside site, portal and app — native.
Account interfaces inside the portal and app — native, when those products are in scope.
Payments inside portal and app — native, when included.
Connected through API where in scope.
The demo is a configurable site, portal and app shell: set structure, content, languages and portal modules; publishing the app to stores is a separate, account-dependent step.
A rWeb environment with web, portal and app configurations.
Structure, content, branding, languages and portal modules.
Content and configuration when production is activated.
A business email and company details. App-store accounts for publishing the app.