Florix Inc. Process Automations

1. Create a Customer Record - Available

Scenario:

Florix Inc. is a global company with over 50 salespeople.

In the past, sellers can directly enter new customer contacts to the company’s Customer Relations Management (CRM) system; however, with a growing customer base footprint of over 1000, it has become a challenging task to ensure accuracy and completeness of the customer records created into the system. This series of inaccuracies is now causing delays in confirmation and billing of orders as finance must wait for sales to reverify the contact details provided in the system. Marketing is unable to derive extract customer insights and deploy proper customer nurturing programs, while management is receiving delayed business reports.

To address this, Florix Inc. decided to implement a CRM record creation approval process and to assign a CRM coordinator to oversee this. With this management expected to not only have clean data, but also to get better classifications and insights to the CRM records.

Process:

  1. Salespeople will initiate a workflow, and fill a basic form and submit for customer creation

  2. CRM coordinators validate the entry by crosschecking with CRM to see any records exists (this should be done manually)

  3. If the record exists, this request will be rejected, and the salesperson will be notified with CRM ID of the customer.

  4. If record does not exist, then CRM coordinator will create the new record and send the success message and the new CRM ID to the salesperson.

Currently workflow will not be integrated with CRM for checking or creating records. Also, there will not be any emails, instead, salesperson will be assigned or present with the status updated in the application itself and when he/she accepts, workflow will be treated as completed.

User groups and Authority:

Sales: All the salespeople will have access to the customer creation request workflow

CRM Team: User group will have “Angie” and her back up “Rozz” for CRM processing, in this case either one of the users in the CRM Team can process the request.

Other similar use cases:

  • Create a new product in Product Master

  • Approve a Social Media post

2. Delivery Gate Pass - Available

Scenario: Florix is an outsourced delivery and servicing company.

This team deliver or bring back, an average of 35 machines a day, to and from its east town warehouse and the service center as new deliveries or for maintenance and repairs.

Its Engineering Manager, Arnold, however, has one major challenge: proper tracking of these deliveries and returns from the shipping and warehouse division.

At present manual gate passes generated by Jude or by deliver teams depending on whether it is a pickup or delivery, are collected and filed physically on boxes, and parked for stock reconciliation until year end. However, once entered into the system, glaring anomalies such as missing information, wrong machine model, and dates can no longer be backtracked due to the lapsed time.

General Manager Barry Mentor requested Jude to implement a digital workflow system to generate the gate passes.

Process:

  1. Gate Pass process will be initiated by shared services or sales team which carry machine information and customer information, based on who receive call or who initiate delivery

  2. If it is a delivery

    1. Warehouse / Shipping will add the serial numbers and other relevant information to the process

    2. Warehouse will prepare and release the item to delivery team

  3. If it is a pickup,

    1. Delivery team is informed

  4. Security will approve the Gate Pass, either the incoming item or outgoing item

  5. Inventory will be updated

User groups and Authority

Shared Services or Sales: “Morris” or “Sales team” will create the request

Warehouse and Shipping will be managed by “Jude

Head of Security: “Bruce” will approve

Delivery Team will action the delivery “Sami”,”Curry

Inventory: Shared Services Supervisor “Robert”

Other Scenarios:

Tallying purchase orders of departments from purchasing team

Request for documents stored in warehouse by shared services team

Customer information sheet/reservation requests/contracts retrieval from real estate clients from sales admin to warehouse division (physical filing cabinets): customer servicing team/ sales manager revert delays

3. Payment Receipts - Available

Scenario: Florix Inc.’s shared services team is responsible for providing various services such as Accounting, Finance, Human Resources, CRM and many other common services to optimize the operational costs. One of those services is the payment receipt reconciliation process. When sales/collection teams have the confirmation of prepayment, either by customers directly deposit the money, or they have a copy of electronic transfer with them. Sales/collection team forward these pieces of paper to shared services team using a WhatsApp or Viber, for initiating the delivery, and later send the originals by a weekly courier to the shared services team.

But the challenges with this have been keeping records of those documents, and many times, people leave with their phone and WhatsApp creating legal and operational challenges. It was not only that but also there has been incidents of missing documents, without any reconciliation. Therefore, the management decided to implement a workflow process to automate the same.

Process:

Sales/collection person will collect the proof of payment or the payment slip (if they received the payment as a cheque or cash then they deposit in our bank)

  1. Create a new workflow item in the system

    1. Attach the document

    2. Fill the basic information

    3. Submit

  2. Document is received by the Shared Services team

  3. Process the Transaction in the ERP (not integrated)

  4. Approve the Transaction

  5. Acknowledge the Salesperson and the Delivery team

Currently the company is not looking at archiving the slips, or automatically updating the ERP. Supervisors' role is to validate ERP entry against the request.

User groups and Authority

Sales: will collect and initiate a workflow Uru”, “Nadia”, “Nimal”, “Jolly”, “Chan”, “Namaskar”

Shared Services Operations Team: Will process the document and enter ERP. Today the team has three people “Morris”, “Andy” and “Sussi

Shared Services Supervisor: “Robert” Will approve or reject the transaction

If Rejected SSO Team will get the task back with some comments.

Other use cases:

  • Simple permit

  • Curfew Pass

  • Laptop/ Device to enter secured area

4. Entry Pass for Visitors - Available

Scenario: Florix Inc., leading technology developer in the recycling space, and Research and Development (R&D) is a key to its leadership. Their main R&D Centre is located inside the Ivy Industrial and Research Park at North Drive and is one of the largest of its kind. The Research Facility consists of advance Microbiology lab researching, advance bacteria cultures that can convert solid waste in rapid time and an Electromechanical Research unit developing advanced helical grinding tools that can crush Rail Tracks.

Entering the facility requires pre-approvals. However, granting permits to enter the facility is still manual- with emails and faxes received by different employees, causing delays in aggregating requests and processing of approvals. To address this, Florix decided to introduce a new entry pass system.

Process:

  1. External visitor sends an email with an attached ID

  2. Relevant user (employee) will apply for the ID

    1. Fill the basic information

    2. Reason

    3. Digital Copy of photo ID

  3. Head of Security will review and approve

  4. Approved Details will be sent to security points

  5. External visitor will receive a PIN number

  6. Visitor will produce the photo ID and the pin number to security

  7. Security will issue an Entry Pass

User groups and Authority:

Employee: is an any employee of the Florix Inc.

Head of Security: Bruce will review the entry and authorize.

You can enhance this case by introducing colored badges. For an example, any request to enter into the Orange area required CEO’s approval before Head of Security.

5. Receipt with Audit capability using enadoc - Available

Scenario:

Florix auditors has made management remarks on the audit statement that payment deposit slips from customers, mostly coming from weekly mails, were not filed properly. No one bothered to file the documents because by the time documents reach the office the process is completed.

To address this, it was decided to have an integrated document management for auditors to be able to access these documents easily. It was also noted that with this system, future disputes that require document retrievals will be easily addressed.

Process:

  1. Salesperson or collection team will collect the payment or the payment slip, if they received the payment as a cheque or cash then they deposit in our bank

  2. Create a new workflow item in the system

    1. Attach the document

    2. Fill the basic information

    3. Submit

  3. Document is received by the Shared Services team

  4. Process the Transaction in the ERP (not integrated)

  5. Approve the Transaction

  6. Document get uploaded to a DMS solution

  7. Acknowledge the Salesperson about outcome via workflow task status

User groups and Authority

Sales: will collect and initiate a workflow

Shared Services Operations Team: Will process the document and enter into ERP. Today the team has three people “Morris”, “Andy” and “Sussi

Shared Services Supervisor: “Robert” Will approve or reject the transaction

If Rejected SSO Team will get the task back with some comments.

DMS accessibility: At present it was decided to keep the access with “Robert” from the SS and “Andrew” from the Internal Audit, but it was not clear who else might need access as well.

Other use cases similar to workflow 26. Simple workflow with an attachment and reply email - Available

Scenario: Sales team of the Florix Inc. was not very happy they had logged in to the workflow system to know when they and learned that they were not updated real time on customer’s payment status: whether it is reconciled and approved. This has been a critical for sales team, as some deliveries are related to the prepayment and until the confirmation, they were not being able to execute the deliveries, thus affecting the customer satisfaction.

The management team of Florix, decided to extend the workflow to send a notification to the salesperson when the process is completed.

Process:

  1. Salesperson/collector will collect the payment or the payment slip, if they received the payment as a cheque or cash then they deposit in our bank

  2. Create a new workflow item in the system

    1. Attach the document

    2. Fill the basic information

    3. Submit

  3. Document is received by the Shared Services team

  4. Process the Transaction in the ERP (not integrated)

  5. Approve the Transaction

  6. Send a mail to the initiated salesperson about the outcome

  7. Document get uploaded to a DMS solution

User groups and Authority

Sales: will collect and initiate a workflow, will receive an email when the process is completed and accepted.

Shared Services Operations Team: Will process the document and enter ERP. Today the team has three people “Morris”, “Andy” and “Sussi

Shared Services Supervisor: “Robert” Will approve or reject the transaction

If Rejected SSO Team will get the task back with some comments.

DMS accessibility: At present it was decided to keep the access with “Robert” from the SS and “Andrew” from the Internal Audit, but it was not clear who else might need access as well.

Other scenarios:

  1. Sales generated proposals to be attached and prompted for review/approvals

  2. Reimbursement approvals

  3. Performance reviews documentation

7. Acknowledge the customer directly using a Formatted Email

Scenario:

Florix Inc.’s new CEO just started his few weeks and when he evaluated the customer lifecycle and servicing process, realized the current business processes is not based on a customer-first approach. Customers did not receive notifications on payment status and processing. He immediately mobilized the team to fix this.

He asked the management team to create a customer inclusive workflow process that keep customers informed throughout the process.

Process:

  1. Collections team will collect the payment or the payment slip, if they received the payment as a cheque or cash then they deposit in our bank

  2. Create a new workflow item in the system

    1. Attach the document

    2. Fill the basic information

    3. Submit

  3. Customer receives an acknowledgement of the process start

  4. Document is received by the Shared Services team

  5. Process the Transaction in the ERP (not integrated)

  6. Approve the Transaction

  7. Send a mail to the initiated salesperson about the outcome

  8. Send customer an email with delivery start

  9. Document get uploaded to a DMS solution

User groups and Authority

Sales: will collect and initiate a workflow, will receive an email when the process is completed and accepted.

Customer: will receive an acknowledgement, means we need the email of the customer as well, either from CRM or from a Table

Shared Services Operations Team: Will process the document and enter ERP. Today the team has three people “Morris”, “Andy” and “Sussi

Shared Services Supervisor: “Robert” Will approve or reject the transaction

If Rejected SSO Team will get the task back with some comments.

DMS accessibility: At present it was decided to keep the access with “Robert” the SS Supervisor and “Jolly” from the SS Audit, but it was not clear who else might need access as well.

8. Assign an engineer to a Task using user picker - Available

Scenario:

Scenario: Florix Inc. is a leading manufacturer of recycling equipment, with a pool of engineers in charge of installation of specialized equipment and servicing requests.

A recurring challenge of Florix is the timely assignment of job orders, processing of installation, and submission of completion reports. Currently, there is no proper process in place to alert Engineering department, all requests are email based, which tends to drown from one department to another, with requesting party not being notified of the status of the request. In this case, sales initiates request, finance acknowledges payment then emails shipping department, shipping department will then deliver the equipment and email the engineering department for installation readiness.

The engineering manager will then assign a specific engineer to be deployed based on availability. Once installed, sales team is informed, and a report is manually requested if required.

Process:

  1. Shipping department will raise a delivery acknowledgement and installation request

  2. Finance will acknowledge

  3. Engineering will allocate and engineer from the Team

  4. Engineer assigned will submit completion report

User groups and Authority

Shipping: Will create the workflow for installation request, “Jude” from the Shipping is responsible for the Same

Shared Services Supervisor: Mr. “Robert” will acknowledge.

Engineering Manager: Mr. “Arnold” will allocate an Engineer from Engineering Team

Engineering Team: has Rocky, Aabar, Kori, Suresi

9. Update parts list in a table when they service job is over - Available

Scenario: Florix Inc has over 20,000 machines installed and running across the world.

To maintain a high level of service, they must have enough stock of spare parts at the service centers. With over 15 models of machines, parts usage tracking across the organization is not easy.

Florix receives over 150 service calls a day. To facilitate these, engineers are required to fill out a paper-based form which contains information on the parts to be used in the service request. Once received by operators, they will manually type the details on to the system to plan for spare parts requisition. However, this tedious manual process led to delays in stock replenishment, ultimately affecting customer service.

To address this, its CEO issued a directive: implement an automated tracking system for engineers request and actual use of parts.

This is to demonstrate the capability of Loops processing of Flowdoh and the Tables update

Process:

  1. Service request will be generated by any one

  2. Service Engineer will be assigned to the Job

  3. Engineer will start Service Job

  4. When the service job is over engineer will add the spare parts list used

  5. When the engineer completes the Job

  6. System should iterate through item list and update a table

User Groups and Authority:

Engineering: Team can start a workflow

10. Parallel processing workflow - Available

Scenario: Entertainment expenses, travel, and sales representation allowances are generally required to be pre-approved if it is over a certain value. However, in Florix Inc’s process, approvals go to audit teams first before it reaches finance. These two approvals are independent from each other and adds time to approval.

The Sales teams has reached out to management and issued feedback that the process is causing delays in getting their reimbursement approvals. Heeding this feedback and to ensure workforce morale, the management team of Florix wanted to find a solution that will allow for parallel approvals from both audit and finance when requests are initiated.

This is to demonstrate the sub workflows and parallel processing capabilities of Flowdoh

Process:

  1. Sales team will create Expense approval request

  2. System will check the Budget availability

  3. If budget is available Parallelly the request will be sent to

    1. Audit

    2. Finance

  4. Once both approvals are in place, Sales will get a notification for spending

User Groups and Authority

Sales: will initiate the workflow for expense approval

SS Finance Team: will approve the request, from SS “Andy” is allocated for this

SS Audit Team: will validate the request for compliance, from Audit “Jolly” is allocated to this

11. Task escalation on purchase request - Available

Scenario: Florix Inc’s Purchasing specialist is Farid. Recently Farid has been assigned with new responsibilities in optimizing the purchasing process, over the top he became a father recently adding some more responsibilities on him. With these changes happening, it was noticed that response time delays to the processing of purchasing requests and thus people start complaining about the same.

Therefore, the General Manager Barry asked the IT team to modify the current purchase workflow to have a time escalation to make sure service levels are being kept.

This will demonstrate the Time-based escalation capabilities of Flowdoh. Please note there are multiple other escalation methods, such as manual escalation using history tab as well as Out of office escalation etc.

Process:

  1. Employees can initiate purchase requests.

  2. It will be approved by Finance Team.

  3. It will be forwarded to Purchasing.

  4. If the Purchasing did not act on the request within 24 hours, it will be escalated to SSO group.

  5. Anyone in SSO group will pick it up and process.

  6. Acknowledge the requester on the delivery.

user groups and Authority

Employees: any one in florix group

Finance Team: Will approve or reject the request based on the internal evaluations.

Purchasing: Will be handled by Farid and will be assigned to him

Escalation will happen if Farid did not respond to the request and escalation will happen to SS Group and someone from SS group can pick up and process.

Send an email to the Initiator with status of Purchase process.

12. Trigger workflow from an Enadoc upload

Scenario: Florix Inc. has outsourced the deliveries to a specialized deliver agent to focus on their core business. However, the responses from the delivery agent takes an additional 24 hours as their field staff only updates delivery status in the evenings.

Florix Inc. also requires a proof of delivery before their engineering team starts customer installation.

Florix Inc. had to automate some workflows to reduce time of reporting and installation.

Process:

  1. Delivery agent field employee, deliver the goods to customer and get the delivery note signed.

  2. He / She captures the delivery note using Enadoc 365 Mobile app in his Mobile phone.

  3. Add few information that is made compulsory by the Florix

  4. Submit it to the Enadoc

  5. Enadoc Triggers the Installation Workflow request

  6. Receive by the engineering manager.

  7. He assigns an engineer.

  8. Engineer will complete the installation report.

User groups and Authority

Delivery Agents: are part of an upload/capture user group in Enadoc, Delivery partner, Delix Transport has four people allocated for Florix. They are “Sami”, “Jerry”, “Notti” and “Currie”

Engineering Manager: Mr. “Arnold” will allocate an Engineer from Engineering Team

Customer: will receive an email, which is being filled by the engineer

13. Trigger workflow from an external web app or form - Available

Scenario:

During one of social events Florix Inc’s CEO attended, he had a chance to speak to one of their customer’s senior managers and was given a feedback that their customer service team was unresponsive about a complaint on a service technician’s behavior. This customer also mentioned that he has made several phone attempts and emails to call out the department’s attention but to no avail.

Taking this complaint constructively, Florix Inc. decided to implement a web-based form for customer feedback. This feedback form encompasses complaint, suggestion or praise, and products which will be forwarded to the human resource department. https://florixfeedback.azurewebsites.net

If it is a complaint, they will check whether there is any HR related activity is there (i.e., a person or incident) otherwise it will be sent to the concerned employees’ department head. If it is a praise then, HR will send a notification to relevant employee and his manager. The customer will receive an acknowledgement email that they have received the form.

If it is a suggestion about product improvement, then the action is passed on to product management team. Which will then be reviewed by general manager. The customer will receive a thank you email for sending the valuable feedback.

Process:

  1. Customer log complaint, suggestion, or a praise via web

  2. Will trigger a workflow and assigned different tasks based on the logic explained above

  3. General manager review

  4. Customer notification

User groups and Authority

Customer: will fill in the form along with his contact details

HR: Manager “John” will act on HR related matters and will involve Reporting Manager if any inquiry which will send emails to relevant people with outcome.

Product: group which has “Tony”, “Conrad” and “Lucy” will review any suggestions before passing it to The General ManagerBarry

Other scenarios:

Marketing job orders once completed, requestor will get a form to rate services or list down suggestions or praise for assigned person.

Job application, once CV is received and submitted by the company, applicant will get notification that the application has been received and later if the candidate was shortlisted or did not make it.

IT Support desk = filling up form for support ticket and prompting IT to acknowledge request and receive feedback once request is completed

Complaint

Complaint and Suggestions

14. Trigger a workflow from an email - Available

Scenario:

Florix Inc. has been in business for over a decade. It has over 35 suppliers, who are supplying components for their manufacturing process. With over 15 different models since inception of the business, it is very normal that some parts are reaching end of life manufacturing and reciprocally, Florix needs to announce parts availability and EOL support for equipment’s they have supplied. With new consumer protection laws, Florix can be sued with heavy penalties if they do not notify customers on time.

The CEO “Jepp” wanted to mitigate the risk by ensuring that the company is alerted whenever a part EOL from supplier is received. However, most suppliers send notices via email, (fortunately there is a standard for that where each email Subject will start with “EOL:”), this was a standard the suppliers adopted in email and now Jepp wants to automate this to create a workflow that will take actions.

This will demonstrate the Email parsing capabilities of Flowdoh

Process:

  1. Outlook email forward rule is defined based on “Subject starts with EOL:”

  2. Mail get forwarded to [email protected]

  3. Flowdoh will be triggered based on incoming mail to the mailbox [email protected]

  4. Based on the part numbers a table will be updated

  5. A decision will be made by the product group about announcements required.

  6. If announcement is to be mail, they will compile it.

  7. General Manager will approve.

  8. CEO will approve.

  9. Marketing will send the communique.

User groups and Authority

Product: group ( “Tony”, “Conrad” and “Lucy”) will receive the email and make the decision to announce EOL for any product

General Manager will approve followed by the CEO

Marketing: department will prepare the final communique, which is headed by “Rozan” and the team “Noel”, “Bing

ONLY PART OF THE PROCESS IS IMPLEMENTED

15. Connecting an app using swagger - Available

Scenario: Florix Inc supply has some sensitive equipment’s that can only be delivered using long open trucks. Therefore, it is very important to know the weather in the city where items are delivered to be known for the drivers to be alerted for necessary packaging and protection.

This demonstrates the Open API integration capability

Process:

  1. Subscribe to a weather service

  2. Create a swagger file to read the weather data

  3. Create a form to request the delivery

  4. Get weather data incorporated to the request

  5. Forward it to the Engineering

Users and Authorization:

Sales: will initiate the delivery request

Engineering team will receive task with weather in the relevant city.

Path to the swagger is here in the Ninja Channel -> General -> Files

More information about the weather map API https://openweathermap.org/weather-data

16. CSS styling for UI enhancements – Available

Scenario:

Florix Inc. has an internal workflow system which is used to optimize their operations. In a recent survey conducted among its employees, it was noted that there was a need to revamp and refresh the user interface of the system as the design was dated.

CEO Jepp has taken this seriously and has asked the Marketing and the IT Teams to enhance the look and feel of the app.

Flowdoh offers multiple ways of customizing the backgrounds of the forms. Including selecting themes and customizing them

Steps:

  1. Select few of those workflows created already

  2. Enhance the look and feel imagination

  3. Implement using CSS styling in the workflow

Users and Authentication:

-No-

17. Workflow with 3rd party signature integration

Scenario: The world has gone into a complete chaos with the COVID 19 crippling social interactions and locking down cities and countries.

Florix was not prepared for a pandemic this big and had to quickly optimize operations by scaling down operations and with the quarantine in place, finding a way to continue remote work set up, facilitating approval with signatures to maintain operations of its skeletal workforce. The CEO, Jepp wanted a digital signature system incorporated into the process and support working from home as ongoing risk mitigation strategy for the company.

Thanks to Flowdoh and Enadoc, along with Microsoft tools he can get most of the operations done. Florix even had implemented remote desktop for their ERP system.

Jepp want digital signature system incorporated into the process and support working from home as ongoing risk mitigation strategy for the company.

Steps:

  1. Create Signatures for all employees

Users and Authentication:

-No-

18. Delegation of Authority and Out of Office - Available

Scenario: Engineering team of Florix Inc. plays one of the key roles of the organization. This keeps all of them really engage and busy throughout the time. But time to time people fall sick and may require taking leave for emergency or personal reasons, the users should be able to delegate their work to a colleague, while they are away.

General Manager and Engineering Manager requested Out of office Notifications for the existing workflows.

With this new feature being implemented, users will be able to mark, out of office when they are not available to take work. Also, they will be able to appoint a person to receive work on behalf of them which will automatically forward the assigned work to the new person, while the out of office is enabled for the person.

Steps:

  1. User logs into the Flowdoh environment

  2. Setup the out of office time and the delegation

  3. When they are back to work, they should remove the delegation

Users and Authorization:

Employees of Florix Inc. can apply Delegation and out of office status.

Engineering Team is the first to enable this feature

19. CRON Jobs

Scenario: Florix Inc. has 20 operating locations with over 200 vehicles and number of machineries. Insurance renewals for these locations, vehicles and worker safety and accident insurances creates a massive load of planning as there is more on expiring municipality licenses, vehicle renewals, rental payments on pre agreed dates and time.

If the above list is not exhaustive enough there are also other contract renewals from suppliers as well with customer.

All this scheduled work today is being manually handled with excel sheets and renewal dates by sorting actioning and re-sorting etc. When counted there were well over 10,000 items a year that should be invocated on a schedule for these processes to happen smoothly.

Florix Inc. Requested Flowdoh to come up with a solution for this. Flowdoh team developed an external application

20. Travel Workflow - Available

Scenario: Florix Inc. being present in 21 countries through partners and its own offices, international travel is a normal activity. With engineers, sales and leadership travelling around to meet clients and to run seminars etc., Florix Inc. Needed a central travel desk to optimize the travel.

However, with separated geographies and different approval levels was complicated enough to look at an automation solution. Genral Manager Barry decided to bring in a global travel workflow using Flowdoh the recent tool they have acquired in process automation. The tool has been very promising as it has automated over 15 different processes and had improve some processes over 50-60%.

Steps:

  1. Any employee who needs to travel will fill a travel request form.

  2. Based on the selection of reporting manager by the employee it will be forwarded to the relevant manager

  3. Based on the approval it will be forwarded to travel desk

  4. Progress will be notified to the user.

  5. Once the travel desk completes it work, it will send all the necessary documentation to the applicant.

  6. Documents will also be archived for the audit and future references.

It was decided that in future this process will be enhanced to identify the budget constraints and reimbursement of incidental expenses to be integrated to the same flow.

Users and Authorization:

All Employees: can apply for Travel

Dynamic user group consisting of all Department Managers and Senior Management is selected as the approvers. CEO – “Jepp”, GM – “Barry”, SSS – “Robert”, EM - “Arnold”, MM - ”Rozan”

Travel Desk: “Bing” from marketing will double for this role for the time being.

21. Loan Calculator – Available

Scenario: Florix Inc. has decided to offer equipment on a loan basis with a nominal interest. In order to automate the calculation of payment installment, it was decided to create a loan calculator for the same.

To implement the same, Flowdoh engineers used excel API to integrate the loan calculation.

Steps:

  1. Sales will submit the value of equipment and the number of installments.

  2. Loan calculator function will calculate.

  3. Send new task with the payment information.

Users: Sales team can initiate and will receive the payment information as well

22. Recordings to Transcribe – Available

Scenario: Florix Inc. a International business provider deals with numerous clients across the globe, With today’s digital age customers and potential Clients often send voice recordings in various languages either from their phones via the use of Speech to Text in Audio format requesting for services, inquiries or praise for the company. To ensure that Florix’s teams specifically sales can respond to each individual request despite the language barrier it was decided to create a Transcribe Application that will translate the language received to the users preferred language in text. To implement this, Flowdoh Engineers used Google’s Text to Speech API to integrate this feat.

Pre-Requisites: 1. Audio File (Currently in this version most consistent File Type is FLAC) 2. Language Codes are Case-Sensitive

Sample MP3 File Text to Speech: https://voicemaker.in/

MP3 to Flac Converter: https://www.online-convert.com/result#j=26edef2b-d245-4316-930b-69e8f2f89403

Language Codes: https://github.com/libyal/libfwnt/wiki/Language-Code-identifiers

Steps: 1. Users will upload the (Audio) File to the Flowdoh Transcribe Forms. 2. Users will select the (Audio) Files, Encoding type & Language code and set to filter any profanities. 3. Once its submitted the Initiator of the workflow will receive the task again and receive a text translation of the audio file used. 4. Users will then select the Language code they wish to use to translate the Audio Files message. 5. Users may proceed to click Archive to Store the message sent to them.

Users: CEO, Wasantha, Bruce and the all of the Sales Teams can initiate the task.

[ Insert Workflow Screenshot Here ]

Last updated