Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 12. Contact Profile & History.md #171

Merged
merged 1 commit into from
Jun 14, 2024
Merged

Update 12. Contact Profile & History.md #171

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/3. Product Features/10. Others/12. Contact Profile & History.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,6 +133,18 @@ It has been observed in some cases, beneficiaries have one phone number and ther

In Glific we have introduced a multiple profile feature, which will help more than one person to create their profiles and use the chatbot to access the information with one phone number.

<img width="995" alt="image" src="https://github.com/glific/docs/assets/143380171/867d0ad7-d748-4eb4-b01a-d0e45ecf0ac1"/>

Profiles are like contacts, where contact fields are saved as key-value pairs in JSON format.

A contact can have multiple profiles, but only one profile can be active at a time.

When the active profile for a contact changes, the fields in the profile are swapped with the contact fields.

At the flow level, the contact fields will be replaced with the values from the active profile's fields.

Profiles are synced to BigQuery in a separate table called "profiles."

Below are the steps on how to implement multiple profile features in your flow.

## Advanced Feature Webinar
Expand Down
Loading