Chatbot Specialist for Automation, Data Cleaning, and Recruitment

We are seeking a skilled Bot-Conversa specialist to enhance and maintain our automated conversational agent. The primary responsibilities will include implementing automation features, ensuring data cleanliness and accuracy, performing regular updates to the bot's functionalities and content, and optimizing its capabilities for recruitment processes. The ideal candidate will have experience in chatbot development, natural language processing, and data management to ensure efficient and effective bot performance.
Alabe imoveis is looking for a single specialist in Bot-Conversa to configure two operations:
cleaning and updating our property database, and agent relationship management/recruitment.
Scoop and Priority :
each operation will have 3 flows: 1 main flow using the official WhatsApp/Meta API and 2 complementary versions for unofficial connections.
Total : 2 official and 4 unofficial flows.
Priority :
deliver the 2 official flows first. Avoid contacting the same person multiple times through different approaches.
Before Budgeting :
Validate the subscription lam, phone numbers, connections, and the centralization of the 3 flows into their respective Kanban.
Inform us to any limitations, alternatives, and extra costs.
Note: 6 flows do not mean 6 different phone numbers. Do not deliver 6 separate boards instead of the two requested Kanban without prior approval.
Property cleaning and updating :
The alabe hub will select the properties to be worked on.
The flow must contact the property owner, confirm availability, and register whether it is for sale, rent, or withdrawn, it must collect changes in price, condo fees, and property tax, (IPTU), optionally ask about other available properties ask about other available properties, and thank them.
Update Kanban
Columns: To content; Awaiting Response;
Did not respond; responses; to verify; completed.
Receiving a reply automatically." Move the card to "responses." Once data collection is finalized, it should automatically route  to "To verify," providing a quick-review summary showing: reference code, reported availability, values, requested changes, and pending items.
There will be not automatic confirmation from the HUB back to BotConversa.
Therefore, entering "to verify" does not require prior review, moving a card to "completed" is strictly manual, done only after verifying it in the hub/CRM.
"To verify" is the second -to last column; "Completed" is the final column. A closed conversation or forwarded data does not mean the update is confirmed. A lack of response should never trigger a property de-listing.
Agent Relationship Management And Recruiment
Alabe will provide a list of known and unknown real estate agents. In this phase, registration, conversation, and follow-ups will stay entirely within BotConversa  without HUB integration. Known and unknown agents will share the same kanban.
Prepare the list import and ensure organization without duplicates. Before sending messages, validate the list's origin and opt-in permission; importing a phone number does not automatically authorize message it.
Agent Kanban.
Columns: To contacts; awaiting response; did not respond; responses; in human support; closes.
Clearly highlight "responses and did not respond." Use tags/fields for: interested requested information, not interested, and opt-out/unsubscribe. Preserve the history and the text action step. Once and agent takes over a chat, pause the bot and any conflicting reminders.
Common Rules And Channels
Configure fields, tags, summaries, card movements, and identify the source flow/number.
Configure operation schedules, intervals and retry limits according to alabe's guidlines. Handle errors, invalid contacts, and late replies; cancel "no-response" reminders as soon as a reply is received.
Respect opt-out and unsubscribes across all flows and numbers, with no further insistence through alternative channels.
Officials Flows:
create, submit, and adjust message templates (message templates/HSMs), respecting category rules, contact permission, and the 24- hour customer service window. Live activation will only happen after template approvals and database validation.
Unofficial Flows:
Explicity state the risks and limitations. Do not promise zero risk of banning or use mechanisms designed to bypass WhatsApp blocks. Activation depends entirely on alabe's authorization.
Delivery and Proposal Requirments
delivery all 6 flows and 2 kanbans directly into alabe's account, conduct tests using authorized contacts, provide documentation of custom fields for raul, and record a practical video explaining the operation.
The video must demonstrate responses, no-responses, opt-outs human handoffs, and the review process. Identify any external dependencies clearly without presenting them as completed task.
In your proposal, include:
your proven experience with similar examples, the timeframe for the 2 official flows and the complete delivery, total price, and post-delivery.