Is There an Existing Issue for This?

• I have searched the existing issues

Where do you intend to apply this feature?

Instill Core, Instill Cloud

Is your Proposal Related to a Problem?

Background

The client information is scattered around in each sale / customer success.

Sales team want to sync the client status.

However, it is usual that sales contact their client with their personal tools.

It is tedious for sales to sync their progress for the team.

Describe Your Proposed Solution

User stories

Story 1

As a sales manager, he/she wants to supervise the status of each client.

Possible pipelines

Concrete example

p.s.

• We have not dug in the details of CRM system, please investigate more details and design a good input & output.

Story 2

As a SEO writer, he/she wants to automate his/her writing. Then, he/she only needs to be a reviewer.

Possible pipelines

Concrete example

Highlight the Benefits

It can solve the problem in the real world.

Anything Else?

Possible components

Note: The sequence means the priority.

Application components

Sales tool

• WhatsApp
• LinkedIn
• Line (only in Taiwan market)
• Gmail
• …

Social media

• Thread
• LinkedIn
• X
• Instagram
• Facebook
• …

CRM (ERP / ERM)

• Salesforce
• HubSpot
• SAP
• …

Reference tools

• cooby (from WhatsApp -> CRM)
• Skott
• https://www.lyzr.ai/jazon/
• https://warmly.ai/

Milestones

1. Read the current pipelines

• https://instill.tech/abrc/pipelines/stomavision
• https://instill.tech/pinglin/pipelines/contract-reviewer
• https://instill.tech/gstrong/pipelines/quickstart

2. Design the pipeline according to user stories.

• Please draw the concrete pipelines first to ask us review before delving into development.
• Timeline: 5 working days

3. Check which components we are missing according to the designed pipeline.

• Please create the skeleton PR first for the incoming components
• Timeline: 2~3 working days

4. Connect those components.

• Timeline: 10 working days

5. Build the designed pipeline after you connect those components.

• Timeline: 1 working day

Note

• About timeline, let's adjust it dynamically if there are much more complicated issues than we think
• Milestone 2~5 is a cycle. Let's finish a whole complete user story first and then iterate it.