Replies and follow-ups

Keep conversations current after the first send.

Sync replies into Vera so the agent can score intent, pause no-reply follow-ups, draft safe replies, and stop when a human should take over.

Inbox

Sync replies into prospect metadata.

Run inbox sync before asking Vera to continue reply work. Synced messages are scored for intent, linked to the matching prospect, and stored as reply metadata the agent can use on the next action.

Reply sync

$ curl -X POST https://api-vera.symph.ai/v1/projects/proj_01hx6x9v2r/inbox:sync \
>   -H "Authorization: Bearer vwk_live_..."

$ curl "https://api-vera.symph.ai/v1/projects/proj_01hx6x9v2r/email-messages?direction=inbound" \
>   -H "Authorization: Bearer vwk_live_..."

Inbound candidates

Turn buyer replies into prospects carefully.

Some inbound messages do not belong to an existing outreach thread. Sync candidates, review the classification, then accept the candidate only when it should become a prospect and reply draft.

Inbound candidate

$ curl -X POST https://api-vera.symph.ai/v1/projects/proj_01hx6x9v2r/inbound-candidates:sync \
>   -H "Authorization: Bearer vwk_live_..."

$ curl -X POST https://api-vera.symph.ai/v1/projects/proj_01hx6x9v2r/inbound-candidates/candidate_01hx8n9jfc:accept \
>   -H "Authorization: Bearer vwk_live_..."

Schedules

Process due no-reply follow-ups.

Production follow-up ticks should be triggered by Cloud Scheduler. Vera skips prospects that replied and queues safe follow-up draft work when the cadence is still valid.

Follow-up tick

$ curl https://api-vera.symph.ai/v1/projects/proj_01hx6x9v2r/follow-up-schedules \
>   -H "Authorization: Bearer vwk_live_..."

$ curl -X POST https://api-vera.symph.ai/v1/projects/proj_01hx6x9v2r/follow-ups:tick \
>   -H "Authorization: Bearer vwk_live_..."