Property management, built natively on Oracle NetSuite

Request a demo

Integrations · Crm & Service

Keep customer context connected

RIOO connects with Salesforce, HubSpot, Intercom and Slack, so marketing, sales, service and internal teams can work in their preferred tools while property and financial records stay in NetSuite.

Why CRM integration matters in property

Large operators often run marketing and sales in a CRM, support in a help desk and internal coordination in chat. Those tools are good at what they do, but they don't hold leases, balances or work orders. Integration lets context flow both ways: a prospect from the CRM becomes an applicant in RIOO, and a support agent sees whether a resident's balance is current.

Why it mattersLeads in silosManual approvalsLease data…Slower, riskiernumbers

What is a CRM integration for property management?

A CRM integration for property management links a sales or service tool such as Salesforce or HubSpot to the system that holds leases, balances and work orders. Marketing keeps its campaigns and attribution in the CRM, while RIOO keeps the applicant, lease and tenant ledger in NetSuite, with agreed fields passed between them.

The value is in the handover points. A prospect who fills in a form on a listing or website becomes a contact in the CRM, then an applicant in RIOO when they ask to view a unit. Once a lease is signed, the CRM can be told the outcome so campaigns stop targeting someone who is already a resident, and revenue attribution reflects real signed leases rather than form fills.

GGross-upEEstoppelSStraight-line rentCCAM

How it works

How does CRM & service work in RIOO?

CRM & service in RIOO runs inside Oracle NetSuite. The properties, units, leases, tenants and vendors it uses are native NetSuite records, so each step updates the same data finance reports on. There is no separate system to sync, and every action keeps an audit trail. The steps below show how the work flows.

Application inMeets criteria?YesNoManual reviewDueAuto-approveInstantSend lease
  1. 01

    Configure

    which records and events are shared, and in which direction.

  2. 02

    Map

    fields between the CRM and RIOO records.

  3. 03

    Operate

    Updates flow between systems as configured.

  4. 04

    Keep the source of truth clear

    Leases, balances and transactions remain authoritative in NetSuite.

How it works

How does a lead travel from CRM to signed lease?

A lead travels in four handovers: capture in the CRM, qualification, conversion to an applicant in RIOO, and a closed-won update back to the CRM when the lease is executed. Each handover is triggered by a defined status change, so neither team re-keys names, unit preferences or move-in dates.

Lease L-2950 · Riverside Lofts3-year term · RetailCaptureStartQualifyMonth 6ConvertYear 2LeaseYear 3Close the loopLease endToday38 months remaining
  1. 01

    Capture

    A web form, listing inquiry or campaign response creates or updates a CRM contact with source and campaign fields.

  2. 02

    Qualify

    Marketing or a leasing agent confirms budget, move-in window and property interest, and sets a qualified status.

  3. 03

    Convert

    The qualified status creates the prospect in RIOO, linked to the property and unit type, where tours, applications and screening happen.

  4. 04

    Lease

    Screening, offer and e-signature run in RIOO; the executed lease and move-in charges post to NetSuite.

  5. 05

    Close the loop

    The lease outcome and start date return to the CRM so attribution and nurture lists stay accurate.

In detail

Connected tools

SalesforceHubSpotIntercomSlackScreeningCRMRIOOon NetSuite

Salesforce

CRM for marketing and sales pipelines.

HubSpot

marketing automation and CRM.

Intercom

customer messaging and support.

Slack

internal notifications and coordination.

In detail

What it enables

Lead handoverShared contextTeam alertsCampaigns

Shared context

service teams see the resident or tenant context they need.

Team alerts

relevant events, such as an escalated request or a large payment exception, reach the right channel.

Campaigns

informed by occupancy and lease expiry data.

Choosing where work happens

RIOO already includes a unified customer view, inquiry tracking and communications logging. Some teams use those natively, while others keep a CRM for marketing. During implementation, we help decide which system owns which step, so you don't maintain the same data twice.

Implementation on NetSuite

TodayUnit 2FLeak under sinkPhoto beforeParts usedPhoto afterResident sign-offPhotos on the jobCaptured on sitePosted to NetSuite

Compare

How do teams put CRM & service into practice?

Teams put CRM & service into practice by configuring RIOO to their own policies, training each role on real scenarios and starting with one property or workflow before rolling out further. The examples below show how that typically looks, from set-up to day-to-day use, and which team owns each part of the work.

The most common integration mistake is letting two systems own the same thing. A simple ownership model avoids that:

Integrations amplify data quality, both good and bad. Agree on required fields, naming conventions and duplicate handling before connecting systems.

TOTypical ownerDistributionSentLLeaseTours today7CCRMOpen tasks16CTConnects to unitsOpen tasks16
StepTypical ownerWhy
Marketing campaigns and lead nurturingCRM (Salesforce or HubSpot)Built for campaigns and attribution
Qualified inquiry and applicationRIOOConnects to units, screening and leases
Lease, charges and balancesRIOO in NetSuiteThe financial system of record
Resident service conversationsRIOO, or Intercom if usedDepends on your support model
Internal alerts and coordinationSlackWhere teams already talk
Reporting on occupancy and revenueRIOO and NetSuiteTies to the ledger

Mapped to NetSuite

Which fields usually map between a CRM and NetSuite records?

A typical CRM integration maps a small set of fields: contact details, lead source and campaign, property of interest, desired move-in date and lifecycle stage. On the RIOO side these land on prospect, tenant and customer records in NetSuite. Mapping fewer, well-used fields keeps the sync reliable and the reports trustworthy.

  1. CRM fieldContact name, email, phoneRIOO / NetSuite recordProspect, then tenant (customer record)One person, one record, deduplicated on email
  2. CRM fieldLead source and campaignRIOO / NetSuite recordProspect source fieldKept for attribution reporting
  3. CRM fieldProperty or community of interestRIOO / NetSuite recordProperty and unit typeDrives availability and pricing
  4. CRM fieldDesired move-in dateRIOO / NetSuite recordApplication and lease startFeeds occupancy forecasts
  5. CRM fieldLifecycle stageRIOO / NetSuite recordProspect, applicant, resident statusUpdated as the lease progresses
  6. CRM fieldCompany account (commercial)RIOO / NetSuite recordCustomer record and subsidiaryLinks multi-site tenants

Explore by topic

Native RIOO tools or an external CRM?

SOD. KimTenant for 5 yrsDepositsRequestsRenewalLeaseMessagesPayments

When RIOO's built-in tools are enough

RIOO includes inquiry tracking, a unified customer view and communication logging. Operators whose leads mostly come from listing sites and walk-ins, and who do not run multi-step nurture campaigns, often find those native tools cover the whole lead-to-lease journey without a separate CRM licence.

When a CRM earns its place

Larger residential operators and commercial landlords with a broker pipeline, account-based marketing or a central call team usually keep Salesforce or HubSpot for campaigns, scoring and attribution. The integration then carries qualified leads into RIOO and results back, so each system does what it is built for.

When a service desk sits in front

Some operators route resident conversations through Intercom so agents can answer common questions quickly. In that model the agent needs read access to balance status, open requests and lease dates from RIOO, while the request itself is still logged against the unit and tenant.

Who is a RIOO CRM integration NOT for?

A CRM integration is not worth building for a portfolio that receives a modest number of inquiries a month and has no separate marketing team. RIOO's native inquiry tracking and communications log will do the job with less maintenance, fewer licences and no field mapping to keep in sync after every CRM change.

It is also the wrong tool for reporting financial performance. Rent, arrears and NOI belong in NetSuite reports, not in CRM dashboards that copy totals and drift out of date. If leadership wants revenue next to pipeline, the better pattern is a NetSuite saved search or SuiteAnalytics workbook that reads the ledger directly.

Strong fitNot a fitFinance-led teamsVacation rentalsRuns NetSuiteEquipment rentalMixed portfoliosNo ERP plannedHonest fit check

What changes

What changes when CRM & service runs on NetSuite?

When CRM & service runs on NetSuite through RIOO, operational work and accounting stop being two separate jobs. Transactions post to the general ledger as they happen, reports use the same records as daily work, and controls come from NetSuite roles and approvals. The changes below are the ones teams usually notice first.

BeforeWith RIOOLeads in spreadsheetsOne lead recordLease data re-keyedLease drives billingRenewals missedRenewals queued
  • Faster lead-to-lease handover
  • Better-informed service conversations
  • Timely internal alerts
  • No duplicate data entrybetween CRM and property records.

Checklist

CRM integration readiness checklist

CRM integration readiness…Agree approval limitsSchedule trainingConfirm data ownersClean tenant recordsMap chart of accounts3/5complete
  • Name one owner for each stage: campaign, qualification, application, lease and service.
  • Agree the unique identifier for a person, usually email, and how duplicates are merged.
  • List the fields that must flow each way and drop the ones nobody reports on.
  • Decide what happens to a CRM record when an applicant is declined or withdraws.
  • Record consent flags per market and confirm they travel with the contact.
  • Test with one property before switching on the whole portfolio.

Talk to a specialist

See CRM & service on your own portfolio.

RIOO connects with Salesforce, HubSpot, Intercom and Slack, so marketing, sales, service and internal teams can work in their preferred tools while property and financial records stay in NetSuite.

FAQ

CRM & service FAQs

Still curious? Ask the team.

Do we need a CRM to use RIOO?

No. RIOO includes inquiry tracking, a unified customer view and communication logging, which cover the lead-to-lease journey for many operators. A separate CRM such as Salesforce or HubSpot is worth connecting when you run multi-step marketing campaigns, a broker pipeline or a central sales team that needs attribution and lead scoring.

Which CRMs are supported?

Salesforce and HubSpot are listed in RIOO's integrations directory for marketing and sales, with Intercom for customer messaging and Slack for internal alerts. Each connection is configured during implementation, including which records and events flow and in which direction. If you use a different CRM, ask whether a custom integration is possible.

Is NetSuite CRM supported?

RIOO runs inside NetSuite, so NetSuite's own customer and contact records are the foundation for tenants and prospects. Teams already using NetSuite CRM features for leads or cases can review with RIOO during implementation which steps stay in standard NetSuite CRM and which move to RIOO's leasing and service workflows.

Where is the source of truth for leases?

In NetSuite, through RIOO. Leases, charges, balances and payments are authoritative in your NetSuite account, and a connected CRM receives only the fields you choose, such as lifecycle stage or lease start date. Keeping the lease in one place prevents two systems disagreeing about rent amounts, dates or who the tenant actually is.

Can HubSpot or Salesforce see tenant balances from RIOO?

Only if you choose to share them, and most operators do not. Balances, charges and payments are authoritative in NetSuite, so a CRM copy can go stale within hours. A common approach is to pass a simple status such as current or in arrears for service context, and keep amounts in RIOO.

How are duplicate contacts handled between the CRM and RIOO?

Duplicates are prevented by agreeing one matching key, usually the email address, plus a rule for which system wins when values differ. Before go-live, existing CRM and tenant data is cleaned so the first sync does not multiply records. Ongoing, new duplicates are flagged for a person to merge rather than merged silently.

Connect your CRM to the records that matter.