Reference Process Flows

detected integrates with many different applications and in many different ways this section covers the common architectures and process flows we see across our client base use them as a starting point for a smooth customer and compliance experience on the detected platform these pages explain who starts onboarding , which of your teams is involved (sales, compliance, customer), and which systems connect to detected pick the flow that fits your journey, open that page for the process diagram, and use the api integration guides https //docs detected app/detected apis/api integration guides when you need endpoint level detail how to choose a flow detected provides case management, the onboarding and verify portals, and the public api you assign your own compliance, sales, and crm staff and connect your systems as needed start with one question where does the journey begin? inside detected your staff or the end customer starts in case management or the detected onboarding portal, before your crm or website creates the case outside detected the journey starts from your website, your crm, or a link you send, detected then runs onboarding, review, and compliance most integrations are external initiated (for example kyb from your own portal, or a crm led flow) detected initiated flows suit teams that create cases in case management first and mainly need webhooks and data sync back into their own systems sales and compliance who does what? sales, compliance, and the end customer have different roles the table below sits alongside the flow picker it is not a separate reference flow stage your sales team your compliance team end customer case created may trigger from crm or send a link may create the case in case management may start alone in the portal before the customer is invited may work in the onboarding portal first and invite the customer later may review the profile before anyone external is invited (crm api flows) n/a during onboarding may support the customer in the portal usually not in the portal completes onboarding tasks after submit often synced via your crm reviews and approves or declines in case management n/a two more questions come up often compliance gate (crm api flows only) must your compliance team review the case before the customer is invited? see crm with compliance review https //docs detected app/detected apis/crm with compliance review or crm trigger to customer https //docs detected app/detected apis/crm trigger to customer sales in the portal will your sales team help progress onboarding in the portal, not only the end customer? that applies regardless of where the profile was created crm, your website, a link, or detected for the documented sales then customer handoff, see internal / customer collaboration https //docs detected app/detected apis/internal customer collaboration choose your flow use the diagram below to narrow down to one reference flow each result links to a dedicated page with the full process diagram data flow \ config theme redux dark look classic layout dagre \ flowchart td start(\[how will you onboard customers using detected?]) start > where{where does the journey start?} where >|inside detected your staff or customer uses detected first| det\[detected initiated] where >|outside detected your website, crm, or emails| ext\[external initiated] det > detfirst{who at your organisation does the first step?} detfirst >|your compliance team creates the case in case management| il\["internally led"] detfirst >|the customer uses the detected onboarding portal on their own| cl\["customer led"] detfirst >|your sales team starts, then the customer completes and submits| icc\["internal / customer collaboration"] ext > extchannel{how do your customers get started?} extchannel >|you send them a link or email| linkfrom{who sends the link?} linkfrom >|your crm sends an automated email| sec\["simple email trigger from crm"] linkfrom >|any other link website, manual email, marketing page| bwl\["using a bespoke weblink"] extchannel >|on your website or app| biztype{what are they onboarding?} biztype >|a business, company kyb| kyb\["trigger kyb from web portal"] biztype >|an individual, identity kyc| kyc\["trigger kyc from web portal"] extchannel >|your crm creates the case using the detected api| compliancegate{must your compliance team review the case before the customer is invited?} compliancegate >|yes, compliance checks first| ccr\["crm with compliance review"] compliancegate >|no, invite the customer right away| ctc\["crm trigger to customer"] at a glance if your journey starts with… flow sales (typical) compliance (typical) your compliance team creating the case in case management internally led https //docs detected app/detected apis/internally led optional creates case, then reviews after submit the end customer using the detected onboarding portal on their own customer led https //docs detected app/detected apis/customer led n/a reviews after submit your sales team starting, and the end customer completing and submitting internal / customer collaboration https //docs detected app/detected apis/internal customer collaboration leads in portal, invites customer reviews after submit a tagged link from your website, email, or another system using a bespoke weblink https //docs detected app/detected apis/using a bespoke weblink optional portal support reviews after submit your web portal, business / company kyb trigger kyb flow from web portal https //docs detected app/detected apis/trigger kyb flow from web portal optional portal support reviews after submit your web portal, individual kyc trigger kyc flow from web portal https //docs detected app/detected apis/trigger kyc flow from web portal optional portal support reviews after submit your crm sending an onboarding email (link only) simple email trigger from crm https //docs detected app/detected apis/simple email trigger from crm often owns lead / email reviews after submit your crm creating the profile via api, with compliance review before the customer is invited crm with compliance review https //docs detected app/detected apis/crm with compliance review may trigger crm, optional portal support gates before invite, reviews after submit your crm creating the profile and inviting the customer immediately crm trigger to customer https //docs detected app/detected apis/crm trigger to customer may trigger crm, optional portal support reviews after submit web portal flows see also trigger a kyb journey with redirect https //docs detected app/detected apis/trigger a kyb journey with redirect and trigger a kyc journey with redirect https //docs detected app/detected apis/trigger a kyc journey with redirect for api implementation detail the flows fall into two groups detected initiating the onboarding in these flows the onboarding process starts inside the detected platform there are often integrations to downstream systems, but those are mainly about updating information in systems such as your crm internally led https //docs detected app/detected apis/internally led your compliance team creates the case in case management customer led https //docs detected app/detected apis/customer led the end customer starts in the detected onboarding portal internal / customer collaboration https //docs detected app/detected apis/internal customer collaboration your sales team starts the application and the customer completes and submits it external systems initiating the onboarding in these flows the onboarding process starts from external systems such as existing customer portals / web apps trigger kyb flow from web portal https //docs detected app/detected apis/trigger kyb flow from web portal , trigger kyc flow from web portal https //docs detected app/detected apis/trigger kyc flow from web portal crms simple email trigger from crm https //docs detected app/detected apis/simple email trigger from crm , crm with compliance review https //docs detected app/detected apis/crm with compliance review , crm trigger to customer https //docs detected app/detected apis/crm trigger to customer website or emails via a bespoke web link using a bespoke weblink https //docs detected app/detected apis/using a bespoke weblink sales may also support customers in the onboarding portal on external initiated flows see internal / customer collaboration https //docs detected app/detected apis/internal customer collaboration for the documented handoff pattern