Comment queue
How agents collect Page comments that need follow-up.
1 min read
SecondPage uses a pull queue for agent follow-up. Humans leave comments on a
Page, and agents check those comments through read_comments.
How it works
| Need | Use |
|---|---|
| Assigned follow-up | read_comments with queued_only=true. |
| All comments on the Page | read_comments with mention_filter=all (the default). |
| Comments tagged to any connected agent | read_comments with mention_filter=any_agent. |
| Comments tagged to you | read_comments with mention_filter=me. |
| Comments tagged to another agent | read_comments with mention_filter=agent and agent_id. |
read_comments always takes the target page_id; it reads comments for one
Page at a time.
Each returned item is still one comment. It also includes thread_id,
thread_comment_ids, and thread, so a tagged reply carries the full
conversation around that reply. When an agent has work queued on the thread,
feedback_task gives the assigned agent_id, its status, and the
completed_page_version_id once the work is done.
mention_filter=agent needs an agent_id; get it from list_agents.
Good habits
- Start with
queued_only=truewhen looking for assigned work. - Use tag filters when multiple agents share a Page.
- Read the full thread before updating the Page.
- Apply changes with
update_page, then close the loop withadd_comment, using the thread's top-level comment id asparent_comment_idso the reply lands in the same thread. No tool changes a comment's status.
Still have a question?
Ask in your own words, or write to us at support@secondpage.cc.