Skip to main content
Configure

Change your onboarding yourself.

Set up products, partners, markets and rules without waiting for an IT release.

Saved versions

Changed by your team

  1. 01PublishedReady for the next application
  2. 02Partner addedA variant saved beside it
  3. 03Product addedQuestions for that product
  4. 04Rule updatedThe earlier version kept

Configure capabilities

  • No-code journey builder

    Questions, documents and the order they appear are settings your team controls.

  • Rules as settings

    The policy is applied as configuration, without a release cycle.

  • Saved and reversible

    Every version is kept, and an earlier one can be restored.

  • Per partner, product and market

    Each customer type can have its own journey on the same platform.

Your team owns the change

A typical onboarding tool ships one flow. When that flow needs to change, the team waits on the vendor. In Wiseflow the journey belongs to your team, and the next application can use it.

Standard onboarding tools compared with Wiseflow
What changesStandard onboarding toolsWiseflow
The journeyOne flow for everyoneA journey for each customer type
Who changes itChanges wait for the vendorChanged by your team
When it is readyAfter a release cycleReady for the next application

Every version saved, and reversible

A question, a rule or a variant can be changed and saved. The earlier version stays on the record, so the team can restore it.

  • Saved versions
  • Who changed it
  • Restore

Version record

Who changed it stays with the version

  • Current version

    In use

  • Earlier version

    Available to restore

A journey for each product, partner and market

The same platform can run a different journey for a product, a partner or a market, without a separate build.

  • Product
  • Partner
  • Market

One platform, separate journeys

  • ProductThe checks that product needs
  • PartnerTheir questions and documents
  • MarketThe rules for that market

Change a provider without rebuilding the journey

The checks stay in the journey. Changing who supplies a check does not mean starting the configuration again.

  • Your contracts
  • Supplied checks
  • Same journey

The journey stays

The provider of a check can change

  1. Check

    Company data

  2. Supplied by

    Your provider, or one Wiseflow supplies

  3. What stays

    The steps, the rules and the record

Configure at a glance

  • Journeys

    • No-code builder
    • Questions and documents
    • Conditional logic
  • Rules

    • Policies as settings
    • Applied to every case
    • No release cycle
  • Versions

    • Every change saved
    • Reversible
    • Recorded
  • Variants

    • By product
    • By partner
    • By market

Next up

Bring us your problem. We'll configure the demo around it.