Recued
Menu
← Back to recipes

Propose customer insight notes from follow-up replies

by recued-core v1 17 views

Use “Propose customer insight notes from follow-up replies” in Recued. It carries out the named workflow using the connections and settings you choose.

How it works 48 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Data fetch
shared_followups ?
existing_proposals ?
Process (46 steps)
existing_proposals_family filter
Filter by condition
response_needed_rows filter
Filter by condition
insight_candidate_rows filter
Filter by condition
already_noted_rows filter
Filter by condition
already_noted_keys map
Extract from each item
unnoted_rows filter
Filter by condition
proposed_thread_ids map
Extract from each item
rows_without_proposal filter
Filter by condition
candidate_rows slice
Take a subset of
pending_count count
Count items in rows without proposal
has_candidate compare
Check if candidate rows has data
defaults defaults
Apply defaults
proposal_key default
Apply default
defaults_2 defaults
Apply defaults
has_response_record compare
Check if response record id has data
has_response_mail_slug compare
Check if response mail slug has data
skip_body_read any
Check if any of the conditions are true
body_read ?
skip: step.skip_body_read equal true
response_body default
Apply default
body_present compare
Check if response body has data
skip_extract any
Check if any of the conditions are true
protect pii-protect
Apply pii-protect
extract_note ?
skip: step.skip_extract equal true
restore_note pii-restore
Apply pii-restore
note_title_raw default
Apply default
note_title trim
Trim whitespace from note title raw
note_body_raw default
Apply default
note_body trim
Trim whitespace from note body raw
raw_insight_type default
Apply default
is_positive_signal compare
Check if raw insight type equals positive_signal
is_objection compare
Check if raw insight type equals objection
is_blocker compare
Check if raw insight type equals blocker
is_commercial_context compare
Check if raw insight type equals commercial_context
objection_or_default ternary
Apply ternary
blocker_or_objection ternary
Apply ternary
commercial_or_blocker ternary
Apply ternary
insight_type ternary
Apply ternary
extraction_confidence default
Apply default
missing_title compare
Check if note title is empty
missing_body compare
Check if note body is empty
below_confidence compare
Check if extraction confidence is less than setting confidence threshold
skip_propose any
Check if any of the conditions are true
write_proposal ?
skip: step.skip_propose equal true
skip_notify any
Check if any of the conditions are true
notify ?
skip: step.skip_notify equal true
card to_summary
Format results as a summary card
Settings 2 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

channels setting = in_app
confidence threshold setting = 0.6

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Permissions it requires

Send notifications
Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.shared

About

Tags

emailmailnotecustomer-insightfollowupconversionproposeclosed-loopwork-queueone-person-companystate:outbound-follow-up-response-watcherpack:outbound-follow-up-responseai_surface

Details

48 steps 2 configurable settings recipe_id: outbound-follow-up-insight-note-from-reply