Skip to content

Commit a859b04

Browse files
goosewingoosewin
authored
Workflow docs revision #2 (#464)
* chore(workflows): move final workflow screenshots to the top * chore: add redirect for old workflows route * feat: add PR template
1 parent 9b8353f commit a859b04

File tree

6 files changed

+35
-26
lines changed

6 files changed

+35
-26
lines changed

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
## Description
2+
3+
<!-- describe the changes as bullet points -->
4+
-
5+
6+
## Testing Steps
7+
8+
- [ ] Run the app locally using `fern docs dev` or navigate to preview deployment
9+
- [ ] Ensure that the changed pages and code snippets work

‎fern/docs.yml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -801,3 +801,5 @@ redirects:
801801
destination: /sdk/web
802802
- source: /workflows/examples/outbound-sales.mdx
803803
destination: /workflows/examples/lead-qualification.mdx
804+
- source: /workflows
805+
destination: /workflows/quickstart.mdx

‎fern/workflows/examples/appointment-scheduling.mdx‎

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,12 @@ Build an AI-powered appointment scheduling workflow that handles inbound calls f
2525

2626
We will be creating an appointment scheduling workflow for Tony's Barbershop, a traditional barbershop that wants to automate their phone booking process with sophisticated branching logic to handle different appointment scenarios.
2727

28+
## Final Workflow
29+
30+
<Frame caption="Complete appointment scheduling workflow with branching logic for booking, rescheduling, and canceling appointments">
31+
<img src="../../static/images/workflows/examples/appointment-scheduling.png" alt="Barbershop appointment scheduling workflow showing conversation nodes, tool integrations, and conditional routing" />
32+
</Frame>
33+
2834
---
2935

3036
## 1. Create a Knowledge Base
@@ -373,8 +379,6 @@ You'll start with a default template that includes a "Call Start" node. We'll mo
373379
</Step>
374380
</Steps>
375381

376-
---
377-
378382
## 4. Configure Phone Number
379383

380384
<Steps>
@@ -402,12 +406,6 @@ You'll start with a default template that includes a "Call Start" node. We'll mo
402406
</Step>
403407
</Steps>
404408

405-
## Final Workflow
406-
407-
<Frame caption="Complete appointment scheduling workflow with branching logic for booking, rescheduling, and canceling appointments">
408-
<img src="../../static/images/workflows/examples/appointment-scheduling.png" alt="Barbershop appointment scheduling workflow showing conversation nodes, tool integrations, and conditional routing" />
409-
</Frame>
410-
411409
## Next Steps
412410

413411
Just like that, you've built an automated appointment scheduling workflow that can handle inbound calls, manage bookings, and provide 24/7 availability for your barbershop.

‎fern/workflows/examples/clinic-triage-scheduling.mdx‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,12 @@ Build an AI-powered clinic receptionist workflow that handles patient triage, ap
2525

2626
We will be creating a triage and scheduling workflow for Riverside Family Clinic, a primary care practice that wants to improve patient access while ensuring appropriate care routing and emergency response through sophisticated workflow automation.
2727

28+
## Final Workflow
29+
30+
<Frame caption="Complete medical triage and scheduling workflow with emergency detection, symptom assessment, and clinical routing">
31+
<img src="../../static/images/workflows/examples/clinic-triage-scheduling.png" alt="Clinic triage workflow showing patient verification, medical assessment nodes, emergency routing, and appointment scheduling" />
32+
</Frame>
33+
2834
---
2935

3036
## 1. Create a Knowledge Base
@@ -538,12 +544,6 @@ You'll start with a default template that includes a "Call Start" node. We'll mo
538544
</Step>
539545
</Steps>
540546

541-
## Final Workflow
542-
543-
<Frame caption="Complete medical triage and scheduling workflow with emergency detection, symptom assessment, and clinical routing">
544-
<img src="../../static/images/workflows/examples/clinic-triage-scheduling.png" alt="Clinic triage workflow showing patient verification, medical assessment nodes, emergency routing, and appointment scheduling" />
545-
</Frame>
546-
547547
## Integrating with Real Systems
548548

549549
This example uses JSONPlaceholder for demonstration purposes. To integrate with your actual healthcare systems:

‎fern/workflows/examples/ecommerce-order-management.mdx‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,12 @@ Build an AI-powered e-commerce customer service workflow that handles order inqu
2525

2626
We will be creating an order management workflow for TechGear Online, an electronics retailer that wants to automate customer service calls and improve order resolution times through sophisticated workflow automation.
2727

28+
## Final Workflow
29+
30+
<Frame caption="Complete e-commerce customer service workflow with order tracking, return processing, and VIP customer routing">
31+
<img src="../../static/images/workflows/examples/ecommerce-order-management.png" alt="E-commerce support workflow showing customer identification, inquiry routing, order tracking, and return processing flows" />
32+
</Frame>
33+
2834
---
2935

3036
## 1. Create a Knowledge Base
@@ -554,12 +560,6 @@ You'll start with a default template that includes a "Call Start" node. We'll mo
554560
</Step>
555561
</Steps>
556562

557-
## Final Workflow
558-
559-
<Frame caption="Complete e-commerce customer service workflow with order tracking, return processing, and VIP customer routing">
560-
<img src="../../static/images/workflows/examples/ecommerce-order-management.png" alt="E-commerce support workflow showing customer identification, inquiry routing, order tracking, and return processing flows" />
561-
</Frame>
562-
563563
## Integrating with Real Systems
564564

565565
This example uses JSONPlaceholder for demonstration purposes. To integrate with your actual e-commerce systems:

‎fern/workflows/examples/lead-qualification.mdx‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,12 @@ Build an AI-powered outbound sales workflow that qualifies leads, handles object
2525

2626
We will be creating an outbound sales workflow for TechFlow Solutions, a B2B software company that wants to automate their lead qualification process with sophisticated branching logic to handle different prospect scenarios and increase appointment booking rates.
2727

28+
## Final Workflow
29+
30+
<Frame caption="Complete outbound sales qualification workflow with lead scoring, objection handling, and automated CRM integration">
31+
<img src="../../static/images/workflows/examples/lead-qualification.png" alt="Sales qualification workflow showing lead lookup, permission-based routing, BANT qualification, demo scheduling, and CRM updates" />
32+
</Frame>
33+
2834
---
2935

3036
## 1. Create a Knowledge Base
@@ -527,12 +533,6 @@ You'll start with a default template that includes a "Call Start" node. We'll mo
527533
</Step>
528534
</Steps>
529535

530-
## Final Workflow
531-
532-
<Frame caption="Complete outbound sales qualification workflow with lead scoring, objection handling, and automated CRM integration">
533-
<img src="../../static/images/workflows/examples/lead-qualification.png" alt="Sales qualification workflow showing lead lookup, permission-based routing, BANT qualification, demo scheduling, and CRM updates" />
534-
</Frame>
535-
536536
## Integrating with Real Systems
537537

538538
This example uses JSONPlaceholder for demonstration purposes. To integrate with your actual sales systems:

0 commit comments

Comments
 (0)