AI Calling Bot - Genesis Document

Explore

Handover Instructions

This is a handover document to walk you through how deployment, testing feedback and support will work.

SsThe app ‘s functionality

As per the scope document, we’ve built an MVP with outbound sales calling (for HRO Today) and related functionality. Below you can find simple guidelines on how the app works, submit your feedback and test out some of the core flows. Enjoy testing it out!

How to access the app

You can access the app at the link below:

⁠

http://fixnewyorkcity.com⁠

⁠

Browser Popup

Username: username

Password: password

Username:

mashood@altventures.co⁠

⁠

Password: password

The purple "built on Bubble" banner at the bottom will disappear when we launch and transfer the app to you, and you put it on a paid plan.

During the testing phase, the app is secured with a password, which we'll remove at launch. This is different from the individual user accounts used to access the app. The credentials for this are given under the heading “Browser Popup” in the blue box above.

In the app, you can only be logged in as one user at any time. To test with multiple users simultaneously, try using different web browsers like Chrome, Safari, Firefox, or Edge for each user.

How to submit feedback

⁠

Play 30 sec video - submitting feedback on the app⁠

⁠

Feedback for the product

To easily report a bug or suggest a feature while testing:

Press on the Purple Chat Icon on the bottom right side of the screen just beside “Built on Bubble”.

Select “Report an Issue”

Write description, highlight section/ record screen.

Press “Submit”

Once submitted, your input will be automatically logged as a new item in our project portal. This allows us to review and address it promptly. Depending on the nature of your request, we will:

Shift it to the DOING section (for bugs we plan to fix).

Place it in the HOLD section (for feature suggestions that are beyond the current scope, which we may consider quoting for later).

Contact you for more details (in cases where the issue is not clear or reproducible).

Providing as much detail as possible will help us resolve these issues more quickly, paving the way for a smoother launch.

Feedback For Call Flow

To give feedback about a specific call (errors, issues, etc.):

Open the campaign detail page

Highlight the call with the issue using Gleap

Write the issue in as much detail as possible (it’ll make it easier for us to convert into actionable)

⁠

If this screenshot does not make sense. Watch the “submitting feedback” video mentioned above and then refer to this.

Voices Selection

Using Google Dialogue Flow allows us to access the following

voices⁠

. On this page, scroll to the following section:

⁠

You can switch “voice type” and “voice name” and then press speak to test any voice. The voice we’re currently using is called “en-US-Casual-K”. You can compare it to other voices.

Moreover, GDF has recently made public its “Custom voice” feature, which we can look into at a later stage if our partnership continues.

Specifics to test

Below is some guidance on how to tackle a few specific flows in the app. This list isn’t exhaustive so you should definitely test the app thoroughly!

Sample CSV for Leads Upload

Please use this sample CSV to upload leads into the platform. For the “Number” field, enter it with the country code but without ‘+’ or ‘00’ before it.

⁠

Sample Leads Upload CSV.csv

69 B

⁠

Flow - 1: Create Campaign

⁠

Creating a Campaign - Loom⁠

⁠

Make sure to logout of any other user first (or use a different browser)

Go to the login page here:

https://fixnewyorkcity.com/⁠

⁠

Once signed in, create a campaign using our sample csv file (feel free to edit it)

Make sure the campaign is created as expected and all the leads are added

Campaign statuses are below:

Status

Description

Scheduled

Lead is scheduled to be called

No Response

Call has been failed on our end and hasn't been received by the lead

Call Failed

Call has been sent but the user hasn't picked up

Call Sent

Call has been sent from our side

Call Started

Call has been started with the lead

Not Converted

Call has been started but the lead has not been converted

Email Resent

HRO Plan email has been resent

Converted

The lead has been converted - can send in a followup by making another campaign before the 8th of March or you can manually followup

Willing for future events

The lead has not been converted but is open to the idea of joining future events

There are no rows in this table

⁠

Flow - 2: Call Reception & Updated Information

⁠

Once campaign is set up, expect to receive calls as per the schedule

Receive and respond to calls as you find appropriate

Check the updated data on the campaign details page

Lead statuses are below:

Status

Description

Scheduled

Lead is scheduled to be called

No Response

Call has been failed on our end and hasn't been received by the lead

Call Failed

Call has been sent but the user hasn't picked up

Call Sent

Call has been sent from our side

Call Started

Call has been started with the lead

Not Converted

Call has been started but the lead has not been converted

Email Resent

HRO Plan email has been resent

Converted

The lead has been converted - can send in a followup by making another campaign before the 8th of March or you can manually followup

Willing for future events

The lead has not been converted but is open to the idea of joining future events

There are no rows in this table

⁠

Deployment Support

We aim to ensure a seamless experience during the initial phase of product deployment. Following the handover, we encourage you to provide feedback on any bugs or technical issues ending on the 1st March. In case of a bug causing a blocker that hinders product testing, please report it immediately via email to a designated team member for swift resolution.

For bugs submitted within the initial one-week testing period, an additional week is allocated for our team to thoroughly address and resolve these issues promptly if we’re not able to solve them till 1st March.

The bug reporting tool integrated with the product is part of the deployment support service and will be available for use until the end of the deployment support.

Support

Deadline

Cost

Collect Feedback and Resolve Technical Blockers

March 1, 2024

Free

Incorporate Collected Feedback

March 1, 2024

Free

Gleap Integration

March 1, 2024

Free

There are no rows in this table

⁠

Upon the completion of the deployment support, extended support and pricing terms will apply for any further assistance required.

Extended Support and Pricing Terms

Support Tier

Details

Resolution Time

Cost Estimate

Passive Support

Team

AI Engineer, 10 Hours, $250.00

No-code Engineer, 10 Hours, $250.00

Overages will be charged at $50/hour

Within 48 hours

$500/month Prepaid

Active Support

Team

Product Associate, 10 Hours, $250.00

No-code Engineer, 20 Hours, $275.00

AI Engineer, 80 Hours, $1,500.00

Overages will be charged at $50/hour

Within 24 hours

$2,125/month Prepaid

Custom Support

Custom Team

Custom Timelines

Custom Pricing

There are no rows in this table

⁠

SsThe app ‘s functionality

How to access the app

How to submit feedback

Feedback for the product

Feedback For Call Flow

Voices Selection

Specifics to test

Flow - 1: Create Campaign

Flow - 2: Call Reception & Updated Information

Deployment Support

Extended Support and Pricing Terms

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.