User Guide

I user guide uses a combination of a Guided Conversation and visual overlays to walk the user through a flow or feature.

Task Chat Branch API

note

These details are only updated with each release, for more acurate updates and keeping track of progress, see the task in GitHub.

---

Feature Details

Team

Owner	Lead
Mendy	Sergey

Status

Doc Status	Product Status	Last Update	Version	Release	Phase
In Progress	Up Next	04.03.2024	0.01	Internal	Alpha

---

Description

Add detailed description

Reminders

Links & Resources

Phases

Phases

Phase One

phase Two

Research

Research

note

the research listed here is spesifict to the Chat feature, for research related to the general Colibri development see the Research document.

Technical

---

Question - Answer -

Conclusion - How do we get data from arenas to form the arena layout and map the devices?

Sources

• [test]

---

Business

User Details

User Stories

Persona One

Update Coming Soon

As a developer I do not want to build out the onboarding for my flow, a simple document with the data I need should generate the onboarding for me

Flows

Personas

Development

Development

All details related to how to build or had been built, how to use, etc are here.

Features

Dependents

Below is a list of features that will be utilized in order to deliver the Guide Executor and it's functionalities.

note

The details bellow are not comprehensive feature details but rather, describe how the features will be utilized within the account, for further details, please see the individual feature documentation.

• Actions

  Create an api to allow apps to add thier own actions in the place of the voice and live actions

• Components

Dependent

These are the feature who repply on the Guide Executor and thier dependents

note

The details bellow are not comprehensive feature details but rather, describe how the features will utilize the Guide Executor, for further details, please see the individual feature documentation.

• Guide

  • Intro

  • Authenication

  • Onboarding

  • User Guide

  • Preferences

Guides

• Intro
• Auth Prompt
• Auth
• Onboarding
• Preferences

Data

On the document we want to keep all the important data, the first fetch and fast to access, all secondary data should be stored on a subcollection and fetch sepratly (if this is cost sfective)

User Accounts should be a top level collection, each account will generate a new document within the "Accounts" collection.

Messages

- Message
- - Message 1
- - - type (offer a fea default options that the client can configure as well as custome options or offer numbered types and allow te client to give each type a title, this will enable the client to offer difrent feature or access levels based on account types)
- - - email
- - - number
- - - legal name (if connected wit a / our identity API this will allow for name/identity varification, useful for saftly and fintech and fraud protection)
- - - age (also opcinaly connect with identity api for varification)
- - - dob (also opcinaly connect with identity api for varification)
- - - varified (true, false)
- - - created (date)
- - - timezone
- - - langages
- - - contact detail

Intelegence

    - names
    - - name 1
    - - - type (legal, nicname, madename, etc)
    - - - name
    - - - laguadge
    - - - created (date)
    - - - varified (true, false)
    - - - varified source (api id)

Identification

    - id
    - - id 1
    - - - type (licence, passport, health card, etc)
    - - - issuer (US gov)
    - - - id number
    - - - status: verified
    - - - issued (date)
    - - - experation (date)
    - - - Verify provider: (api id)
    - - - Verify date: log id
    - - - image
    - - - id_proof`

Condissions

    - Sessions
    - - Section #1
    - - - auth type (OTP, Google, Apple, Normal)
    - - - device_type (Android, IOS, Web)
    - - - device_token
    - - - location
    - - - activated (date)
    - - - status (active, inactive)
    - - - inactive (date)

Knowladge

Envierment

• location
• mood
• tone

Preferences

- prefrences
- - communication
    - - - method (push, email, text)
    - - - default (true, false)
    - - - allow (true, false)
    - - - block (true, false)
    - - - level (all, update, security, system)
    - - - channels (id, id, id)
    - - privacy
    - - - allow (true, false)
    - - - block (true, false)
    - - - allow user data collection (true, false)
    - - - allow user data share (true, false)
    - - - allow user data anonymize (true, false)
    - - - allow user data deletion (true, false)