Home

Deploying Your Invevo System.

Your Invevo System is referred to as a Tenancy. We typically name it after your company, or company + region - for example, “invevoglobal” for an umbrella Tenancy or “invevouk” for a regional/purpose-specific Tenancy.  

A single global Tenancy centralises your portfolio - one set of dashboards, shared workflows and integrations, and reporting aggregated in one place. Regional Tenancies provide clean separation and access rights between systems - supporting data residency, local processes and integrations, lower latency for local users, and failure isolation.  

Rule of thumb: choose global for unified visibility and consistency; choose regional when you need strict separation, compliance, or regional autonomy. 

Ingesting the Data

Invevo ingests data via two methods, SFTP or API.

SFTP

Files are send into an SFTP folder which we retrieve them from.
 
File Types: CSV but is delimiter agnostic. 
File Format: Text file which has UTF8 encoding. 
We provide: Location, Username and Password

API

Summary:

Only the time allowed for design, build, and UAT varies.

Your Implementation

Every Invevo project follows one of three plans. The outcome is the same, we deploy a Baseline system, Design, Build, Test and Go Live.

Express (2 weeks)

Outcome: fastest time to value with leveraging proven functionality.

Week 1: data and small design changes

Week 2: build Mon/Tue, test Wed/Thu, go live Fri.

Standard (4 weeks)

Outcome: a balanced, tailored and tested rollout

Week 1: Onboarding and Data

Week 2: Design

Week 3: Build

Week 4: Test and go live

Extended (6 weeks)

Outcome: Deeper design and longer UAT

Week 1: Onboarding and Data

Weeks 2 and 3: Design

Week 4: Build

Weeks 5 and 6: UAT and Go Live

We will open each Project with a Project Kick Off Session that Includes:  

  • Introductions & logistics 

  • Objectives, scope, success criteria 

  • Delivery plan & key dates 

  • Roles & responsibilities (RACI) 

  • Environments, access, data readiness 

  • Risks & dependencies 

  • Actions, owners, next steps 

  • Discuss Next Steps and Requirements 

What is Baseline?

A ready-to-go Invevo configuration that ships with best-practice workspaces, automation, reports, and tooling. It reduces design effort, shortens implementation time, and lets us focus on your tweaks rather than building from scratch.

What’s included out of the box:

Workspaces

Collector Workspace: customer and transaction lists, tasks, KPIs, email inbox, filtered to each Collector

Manager Workspace: Visability across the team, KPI's, workload and easy to resolve escalations.

Team Stand-up View: review output against targets, raise escalations for review and agree on to todays priorities.

Optional add-on: Invevo Protectfor credit risk reporting and a richer customer risk view. Priced as a seperate module.

User Toolkit

Customer 360: a single view of all customer data in one place, for informed actions

Email Builder: prebuilt templates and a simple to use editor for new templates.

Tasks: manual task creation plus automatic tasks from system events

AI translations: leverage AI to read and send communications in any language to support global systems and client-bases.

Customer Self-Serve Portal: end customers can view their account summary, create tickets and most importantly checkout, without intervention required.

Business intelligence

Data that drives action. Track KPIs, company objectives, and trends to review initiatives and forecast outcomes. Make changes yourself in the tool and see the impact fast.

Financial reporting: revenue and collections trends for outcome control and forecasting

Productivity reporting: workload, throughput, and efficiency across tasks, emails, and disputes

Automation and Orchestration

Dunning strategies: best-practice templates ready to run

Task automation: triggers for common events such as broken promises

Cross-workspace communication: escalations and updates flow to the right place

What this gives you

  • A reference design you can react to and refine
  • Working functionality across the full feature set on day one
  • Prebuilt analytics to measure, learn, and improve financial outcomes

How go from Baseline to Go Live?

To Go Live with the Baseline build we need to:

Get Data into the system, understand the user community and how automation can support them.

We neatly have collated these requirements into 3 distinct sessions with requirement packs to complete for each.

 

Business Outcome

Requirement

1. Data

Clear view of the data landscape

 

Completed Data Schema

2. Roles and Responsibilities

Walkthrough the day in the life of each persona

Documented personas and their assignments, escalations, approval SLAs, and KPI’s.

3. Automation and Workflows

Clarity on how we can support each persona with Invevo Flow

Documented email templates, workflows, and strategies.