SANDBULL AI helps owners of trades and local service companies install the AI and automations that already work in their shop. We need a US-based contractor we can pull onto specific client projects as they close. Not a retainer seat. Not a full-time hire. When a project is live, you jump on it, ship it, and we close that ticket. What you will actually do Turn an audit into a build: follow-up sequences, booking, dispatch or estimate flow, inbox, CRM, simple internal tools Connect the stack the client already has (often GoHighLevel, plus whatever they run for jobs, phone, and payments) -Write the SOPs so the owner and their people can run it without us -Join short client calls when we need the implementer in the room -Flag what is out of scope before you start clicking This is not -A sales role -A “prompt engineer” or ChatGPT-wrapper gig -Agency account management - Building our marketing site Must be true -You live and work in the United States (we will only hire US) -You have shipped AI or automation inside real service businesses, not just SaaS demos -You can work from a written brief and a Loom, and you do not need daily standups -You can write clearly to a 50-year-old shop owner -You are fine with project billing (fixed per project or a capped hourly block, we decide per job) Nice if true GoHighLevel, Zapier or Make, and one of: AccuLynx, ServiceTitan, JobNimbus, Housecall Pro, or similar You have sat on a call with a contractor or home-services owner before How to apply Do not send a generic cover letter. In your proposal, take a loom/video and answer these three: 1. One AI project you actually shipped (what you installed, what changed) 2. The tools you used 3.Your hourly rate and a ballpark for a 2-week implementation 4. A goal you are currently working towards in your life. If those are missing, we will skip the proposal.

##SITUATION We are a boutique, family owned SEC registered RIA serving high net worth families. About 15 people. We run Salesforce Financial Services Cloud, Microsoft 365. I already build with Claude daily: custom skills, projects, MCP connectors, and generated deliverables. What I do not have is a governed system. Brand tokens live in three places. Document output quality depends on who prompted it. Nothing is versioned. Nobody else at the firm can produce a client ready artifact without routing it through me. You will design that system, build the first production version of it, and train me to own and extend it after you leave. If your plan requires you to stay forever, you are not the right fit. ##SCOPE 1. Firm wide Claude design system Condense and build a single governed source of brand truth that every Claude output pulls from. - Brand token file (colors, type scale, spacing, logo rules, chart palettes) structured so it can be consumed by document generation, HTML, and Salesforce components - Skill and project architecture: what belongs in a skill, what belongs in a project, what belongs in a shared reference file, and how they call each other - Naming, versioning, and backup conventions - A written standard I can hand to a new hire 2. Training and handoff on schema and structure - Live sessions (recorded) teaching me how to add, update, and retire skills and reference files without breaking downstream output - A maintenance runbook: what to review monthly, what breaks first, how to test a change before it goes firm wide - Debug patterns for when generated output drifts off brand 3. Document generation pipelines Repeatable, prompt driven production of: -Simple one page formatted outputs (client summaries, meeting recaps, one page briefs) -Complex 20 to 30 page client reports with cover pages, section dividers, running headers, table of contents, charts, and disclosure pages -Excel styles and templates (formatting standards, conditional formatting rules, chart theming, reusable model shells) - Fillable PDF and word docs Each pipeline needs a defined input, a defined output file format, and consistent formatting across runs. Show me how you handle page breaks, chart theming, and long document assembly, because that is where most of these builds fall apart. 4. HTML and LWC component system - Branded HTML component library for microsites, forms, and email friendly layouts - Lightning Web Component patterns for Salesforce Financial Services Cloud that inherit the same tokens, respect SLDS, and pass a Salesforce code review - Documented so Claude can generate new components on pattern rather than improvising 5. Account Engagement email template and block library Salesforce Account Engagement (formerly Pardot) is our marketing automation platform. We need a branded, reusable email system inside it. - Master email template set: newsletter, event invitation, client announcement, advisor introduction, drip and nurture, plain text style personal send - A block or region library our team can assemble without touching code: hero, headline plus body, two column, advisor bio card, event details, CTA button, disclosure footer, social footer - Email safe HTML that renders correctly in Outlook desktop, Outlook web, Apple Mail, Gmail, and mobile, including dark mode behavior - Merge field and dynamic content handling, correct unsubscribe and preference center links, and required disclosure blocks -Tokens inherited from the same brand source as every other output, so a color change happens once - A Claude pipeline that turns a draft or a content brief into a populated, ready to load template Tell me which Account Engagement email builder version you have built in and how you handle testing across clients. We have an existing internal process that converts .eml files into Account Engagement ready HTML. You may extend it or replace it, but say which and why. 6. Voice and positioning system for text generation Codified tone rules by scenario, with examples and counterexamples: - Client email replies - Internal updates and status notes -Client proposals and pitch material - Marketing and newsletter copy - Compliance sensitive language and phrases we never use Deliverable is a voice reference plus the prompt structure that enforces it, not a style essay. 7. Deployment and administration on a Claude Team plan Rollout plan across roles: advisors, planning, operations, service Seat structure, org level feature toggles, and connector policy Adoption plan with training material by role Documented guidance on what can and cannot be restricted at the Team tier, and a recommendation on whether Enterprise is justified for us Compliance context We are SEC registered. Anything client facing is subject to books and records retention and the SEC Marketing Rule. Your build needs to account for review before distribution, source citation in generated reports, and clear rules on what client data may enter a prompt. Prior experience in financial services, legal, healthcare, or another regulated industry is a strong plus. Deliverables checklist Brand token source file plus consumption pattern for each output type Skill and project architecture map with naming and version standards Four or more production document pipelines (one page, long form report, Excel template set, and one of your recommendation) HTML component library plus LWC component patterns with sample code Account Engagement master templates plus a reusable block library, render tested across major clients Voice and positioning reference with scenario prompts Team plan rollout plan, permission configuration, and role based training material Recorded training sessions plus a written maintenance runbook A 30 day and 90 day extension roadmap You are a fit if you have Shipped production Claude skills, projects, or agent systems for an organization, not just personal use Built document generation pipelines that produce polished, repeatable, multi page files Strong design system fundamentals: tokens, components, documentation Working knowledge of Salesforce Lightning Web Components and SLDS Production email HTML experience, including Outlook rendering, dark mode, and marketing automation template systems Comfort writing documentation and teaching a technical but non engineer operator Opinions. I want someone who tells me when my structure is wrong ##Bonus points Financial services or RIA experience Salesforce Financial Services Cloud specifically Salesforce Account Engagement or Pardot template development Excel or Word template engineering at a high level of polish Experience administering a Claude Team or Enterprise deployment

We are launching an AI workflow consulting service for small and midsize businesses, initially focused on financial advisory firms, fintech companies and other professional-services businesses. We are looking for a smart, practical AI Workflow Consultant who can help us understand how a client currently operates, identify processes that could be improved and build simple, reliable AI-enabled workflows. This is not primarily a software-development role. We need someone who is excellent at understanding business processes, simplifying them and translating them into workflows using tools such as ChatGPT, Claude, Zapier, Make and other no-code or low-code platforms. Our founder will source clients, lead the sales process and run the initial conversations. You will participate in client assessment calls and take the lead on converting what we learn into an actionable workflow roadmap and working solutions. What You Will Do Participate in 15-minute introductory AI assessment calls with prospective clients Join deeper paid workflow-assessment sessions Ask thoughtful questions about how work is currently completed Map existing processes, including steps, systems, decisions and handoffs Identify repetitive work, bottlenecks and opportunities for AI assistance Rank opportunities based on potential impact and implementation effort Recommend practical tools and workflows Simplify inefficient processes before attempting to automate them Build reusable prompts, custom GPTs, Claude Projects, Claude Skills or no-code workflows Test workflows and refine them based on client feedback Create clear standard operating procedures and training materials Help train client employees to use the finished workflows Coordinate with our developer when a project requires custom technical work Work with our client-service manager to keep projects on schedule Support one active workflow improvement at a time for each client Examples of Potential Workflows Turning meeting notes into summaries, action items and follow-up drafts Preparing client-meeting briefs using approved source materials Repurposing newsletters into emails, social posts and video scripts Creating first drafts of recurring client reports Organizing prospect or client onboarding information Classifying and scoring marketing leads Creating internal knowledge assistants using approved company materials Converting calls or voice notes into structured content drafts Drafting CRM notes and recommended follow-up tasks Documenting repeatable internal processes What We Are Looking For Strong practical knowledge of ChatGPT and/or Claude Experience building AI-assisted business workflows Strong process-mapping and problem-solving skills Experience with no-code tools such as Zapier, Make or similar platforms Ability to understand how a process works before recommending technology Excellent written communication and documentation skills Comfort participating in client-facing calls Ability to explain AI workflows to nontechnical users Good judgment regarding privacy, sensitive information and human review Ability to work independently and deliver against defined acceptance criteria A bias toward simple, maintainable solutions instead of unnecessary technical complexity Experience with financial services, RIAs, fintech, marketing agencies or regulated businesses is helpful but not required. What This Role Is Not It is not a traditional software-engineering position. It is not a role for someone who only provides high-level AI strategy. It is not about building complicated automations when a simple solution will work. It is not an hourly advisory engagement with undefined deliverables. We need someone who can diagnose a process, build the solution, test it, document it and help the client adopt it. Engagement Structure This will begin as a project-based contractor position. We expect to approach three to five existing clients and initially close a small number of pilot engagements. Compensation will be based on completed deliverables rather than hours worked. Before each project begins, we will agree on: The workflow being addressed The expected deliverable The acceptance criteria The fixed payment The anticipated delivery date Initial projects may include: Participating in an AI Workflow Assessment and helping produce the client’s prioritized roadmap Building and documenting one defined AI workflow Supporting the client through testing, training and adoption Continuing with additional workflows through a recurring client engagement If the pilot is successful, this could grow into consistent ongoing work across multiple client accounts.

Type: Hourly, ongoing (part-time to full-time, room to grow) Stack you'll work in: Notion, Slack, HubSpot, Google Workspace/Gmail, Claude + other LLM APIs, Zapier/Make/n8n About us We're a fast-moving sports and fan-engagement startup. We're small, we ship quickly, and we want AI woven into how the whole company operates, not as a side experiment, but as the default way we work. You'd be the person who makes that real. What you'll do Map our current workflows across sales, marketing, ops, and content, then find the highest-leverage places to automate. Build automations and agent workflows that connect our tools (Notion, Slack, HubSpot, Gmail/Google Workspace) using platforms like Zapier, Make, or n8n plus LLM APIs. Design and ship AI agents for real jobs: lead routing and CRM enrichment, content drafting, customer/fan response triage, internal knowledge search, reporting digests. Stand up the connective tissue (prompts, integrations, guardrails, and monitoring) so automations are reliable, not brittle demos. Train and enable our team: build SOPs, run working sessions, and create lightweight docs so non-technical people actually adopt what you build. Help set our AI strategy and roadmap as we scale. You're a strong fit if you Have shipped real automations and AI agent workflows in production (not just prototypes). Are fluent with Zapier / Make / n8n and at least one major LLM API (Anthropic/Claude, OpenAI). Know your way around HubSpot, Notion, Slack, and Google Workspace integrations and APIs. Can write clean prompts and think in systems: edge cases, error handling, human-in-the-loop checkpoints. Can explain technical work to non-technical people and get them to adopt it. Communicate proactively and move fast without breaking trust on things that touch customers or revenue. Nice to have Experience taking a small company "AI-native" end to end. Background in sports and/or blockchain. Comfort with light scripting (Python/JS) when no-code hits its limits. How to apply In your proposal, please: Describe one AI agent or automation you built, the tools involved, and the measurable result. Tell us how you'd approach training a non-technical team to actually use what you build. This part matters as much as the build. Share your hourly rate and weekly availability. Proposals that skip these will be passed over. We're looking to start with a small paid task and grow the engagement from there.

We have two workflows we're looking for support in creating for our agency. Workflow 1 – Call Transcript to Recap and Email Workflow Overview We are seeking an AI/automation consultant to help our business development and account team automate the process of turning call transcripts into a standardized recap and a draft follow-up email, triggered automatically when a call concludes. This workflow is being requested by business development and account teams but will be built and maintained by operations on their behalf. Current State When a call concludes, the business development or account team member manually takes the call transcript and pastes it into ChatGPT or Claude, prompting for a call recap and a follow-up email. This is done ad hoc, without a standardized recap format or consistent prompting approach across all team members, and depends on the individual's own prompting skill and time. Claude has a native connector to Fireflies. It is not known whether a similar ChatGPT integration exists. The team is open to a third-party connector/automation platform (e.g., Make.com) if needed to run the workflow seamlessly in the background. The team would consider working with Claude if a method exists to meaningfully improve tone replication (e.g., prompting techniques, saved style guides, or a Projects-style setup); otherwise, ChatGPT is preferred for this step due to stronger perceived creative writing capability. Desired Future State A workflow that triggers automatically when a call (recorded via Fireflies, our AI notetaker) concludes. The workflow pulls the transcript and produces two outputs: A call recap in a standardized format (we will provide the output format) for the internal team A draft follow-up email in Outlook, written in the voice of the notetaker owner (the BD/account person on the call). This would be written for the attendees of the meeting and be created in a standard format (which will be provided). Scope of Work 1. Interview business development lead on the current state and future state requirements for the workflow output. 2. Assess and recommend the integration/trigger approach: determine best way to connect Fireflies, the chosen AI tool (ChatGPT and/or Claude), and Outlook/Word, including whether a third-party automation platform (e.g., Make.com) is needed to run the workflow end-to-end 3. Assess and recommend the AI tool/integration approach for tone-sensitive email drafting: including whether prompting, custom instructions, or a “Project”-style setup in Claude could close the tone-replication gap, versus routing this step through ChatGPT. If no clear improvement path exists for Claude, ChatGPT is the team's preferred default for this step. 4. Advise on build approach and provide implementation guidance: the consultant will design and advise; our operations team will handle hands-on implementation on behalf of the business development and account teams, who will be the end users of the workflow 5. Coach both audiences: business development and account team members on how to use the workflow day-to-day (e.g., what to expect, how to review/edit outputs before sending), and the operations team on maintaining and troubleshooting the automation itself. Training approach and cadence to be proposed by the consultant based on the final integration design. Technologies Fireflies (AI notetaking, paid) ChatGPT (paid) Claude (paid) Outlook (email) Word (recap documentation) Ideal Consultant Experience with automation/integration platforms such as Make.com, Zapier, or similar Experience with AI notetaking tools generally (Fireflies or comparable) Strong prompt engineering/AI writing tone-matching experience Experience with Outlook/Microsoft 365 automation Comfortable in an advisory/architect role rather than hands-on development. Success here means our team can implement and maintain the solution independently, with the consultant guiding decisions rather than writing the build. Timing Target start: August 2026. Targeting completion within Q3 2026, with the understanding that implementation pacing depends on internal team bandwidth alongside other priorities. No hard deadline. How to Respond Brief summary of relevant experience and 1-2 case examples, particularly with automation platforms (Make.com/Zapier) and/or AI notetaking or transcript-based workflows Proposed approach and phasing for scope items 1-5, including your recommended approach to the ChatGPT vs. Claude tone-replication question (item 2) Estimated timeline and cost Any clarifying questions Workflow 2 – Business Development Brief & Proposal to Scope of Work Automation Overview We are seeking an AI/automation consultant to help our account team automate the drafting of a Scope of Work (SOW) document from a business development brief and proposal deck. This would be triggered on demand by the account person, with the ability to specify which pricing tier and buy-up options the client has selected. This workflow is being requested by the account team but will be built and maintained by operations on their behalf. Current State Scopes are drafted manually, pulling details from the business development brief (Word) and proposal deck (PowerPoint). A previous scope is typically saved as a copy to preserve formatting and used as the starting point, then customized to the new engagement. Scopes follow a standardized format, documented clearly in an existing template, which can be provided to the consultant directly. Business development briefs contain the solution design which dictates tiered packages and buy-ups for the proposal. The business development briefs tend to be inconsistent due to the number of contributors involved in drafting it, however the proposal deck follows a consistent format across engagements. Desired Future State A structured environment (e.g., a Claude Project or comparable setup) pre-loaded with the standardized scope format and drafting instructions, where the account person inputs the business development brief and proposal deck, and directs in plain language which pricing tier and buy-up options the client selected (e.g., “client selected Intermediate plus the Concepting buy-up”), and receives a drafted scope of work (Word doc) in the standardized format for refinement. If it is not cost prohibitive, this word doc would save to the appropriate location within our SharePoint structure for editing. Scope of Work 1. Design and configure a structured project/workspace (e.g., a Claude Project or comparable setup) pre-loaded with the existing standardized scope template and drafting instructions, so the account person doesn't need to re-explain the format or process each time 2. Assess the business development brief and document what needs to be true within it (structure, required fields, level of detail) for it to be reliably usable as an input for scope drafting 3. Advise on build approach and provide implementation guidance: the consultant will design and advise; our operations team will handle hands-on implementation on behalf of the business development and account teams, who will be the end users of the workflow 4. Coach both audiences: business development and account team members on how to use the workflow day-to-day (e.g., what to expect, how to review/edit outputs before sending), and the operations team on maintaining and troubleshooting the automation itself. Training approach and cadence to be proposed by the consultant based on the final integration design. Technologies Word (business development brief, SOW) Power Point (proposal deck) ChatGPT (paid) Claude (paid) SharePoint (file server) Ideal Consultant Familiarity with Claude Projects or structured AI workspaces Comfortable in an advisory/architect role rather than hands-on development. Success here means our team can implement and maintain the solution independently, with the consultant guiding decisions rather than writing the build. Comfortable working with data within our existing paid AI tool environment Timing Target: complete within Q3 2026. How to Respond Brief summary of relevant experience and 1–2 case examples, particularly with Claude Projects/structured AI workspaces and document extraction from Word/PowerPoint Proposed approach and phasing for scope items 1–4, including your recommended approach to documenting business development brief requirements (item 2) Estimated timeline and cost Any clarifying questions

I'm looking for a high energy, highly motivated person who is very interested in learning all about AI and how it's already changed the impact of Marketing. We have several companies that require a dedicated committed and high energy individual with initiative. This is a full-time job with a focus on training to enjoy a long-term relationship. If this sounds like something that you would like to pursue, please contact me right away.

We’re looking for US-based freelancers to support ongoing AI training and evaluation projects. The work primarily involves reviewing AI-generated responses, comparing answer quality, and providing clear feedback that helps improve AI models. What you’ll do Review and compare AI-generated responses Evaluate responses for accuracy, relevance, reasoning, and overall quality Select the better response based on project guidelines Write short, clear explanations for your decisions Identify factual, logical, or instruction-following issues Follow detailed project-specific evaluation criteria Requirements Currently based in the United States with valid US work authorization Strong written English and reading comprehension Good attention to detail Able to follow detailed instructions consistently Comfortable working independently with online tools Preferred, but not required Previous experience with Outlier, Handshake, DataAnnotation, Scale AI, or similar AI training platforms Experience with AI response evaluation, data annotation, QA, or content review Software development or other technical background Bachelor’s degree Previous AI training experience is helpful, but not required. Candidates who can think critically, follow instructions carefully, and explain their reasoning clearly are encouraged to apply. Some projects may require a short AI-based interview, assessment, or qualification task before work begins. When applying, please briefly tell us about your background and any relevant experience with AI training, LLM evaluation, Outlier, data annotation, quality review, or technical work.

WHO WE ARE InCon Process Systems designs, fabricates, pilots, and supports wiped-film and short-path distillation systems. We are a specialty manufacturer in the western Chicago suburbs with about seven employees. The company is engineering-heavy and we have no dedicated IT department. Our team already uses Claude in the browser and is comfortable with it. We are not starting from scratch, and we are not looking for someone to explain what AI is. WHAT WE WANT Two things, in this order. First, expand what our team can do — we want our people using AI across more of their daily work and using it well. Second, move reliable work off people's plates. Where the tool can handle something dependably, it should. Where the work takes judgment, our people keep it. One measure we'd use six months out: fewer customer inquiries sitting too long before someone responds. PHASE 1 (about one month) 1. Configure Claude connectors for Gmail, Google Calendar, and Slack. Slack scoped by explicit allow-list of channels, not a deny-list. One channel excluded. 2. Build a recurring Project Status and Action Summary. Open items and completed items over a trailing one to two weeks, plus upcoming meetings with context on what each concerns. It should track what we owe others and what others owe us, identify likely owners, and flag unanswered customer inquiries, stalled work, and emerging risks. Uncertain conclusions should be separated from established ones. Important: we have no project management system, no CRM, and no tracking software. Project status currently lives spread across email, Slack, and people's heads. The digest is not summarizing a list that already exists — it has to build the project picture out of ordinary communication. That is the point of it, and it is the difficult part. 3. Role-based visibility. Each user gets a personalized view of the work they're involved with, delivered by Slack DM. A single company-wide summary for everyone is not sufficient. CEO and President get company-wide visibility and should be able to ask cross-company questions on demand — what's behind, what's due, what we're waiting on, what looks at risk. 4. Where the system identifies work needing attention and has enough context, it should prepare a next step for human review — a follow-up, an acknowledgment, a request for missing information. Nothing sends or changes anything externally without our review and approval. If information is insufficient, say what's missing rather than inventing an answer. 5. Discovery interviews with our users, one at a time. Not as a group, not through a single point of contact. We want you to understand what we do well enough to suggest things we haven't thought of. This is paid work, not part of your pitch. 6. Training and a written runbook. Our people are technically capable and learn quickly — teach the architecture, not button-clicking. Our internal IT staffer needs enough to handle first-line questions, but is not taking ownership of this system. 7. A written recommendations document for what we should do next. This carries real weight in how we evaluate the engagement. OUT OF SCOPE FOR PHASE 1 Standalone quotation drafting. Meeting capture and transcription (note: meeting outcomes later documented in Gmail or Slack are in scope). Dropbox and local file integration. Automation platform work — n8n, Make, Zapier. Chatbots, voice agents, customer-facing deployments, software development. Everyday writing help — someone asking Claude to tighten an email — is ordinary use of the tool. That needs training, not development. Please don't quote build hours for it. THE ONGOING ROLE — READ THIS This matters more than the build in deciding fit. We want someone who checks in regularly with our users to hear what they're doing, what they want to do, and what they could be doing better, and turns that into improvements. Monthly to start, with a strong expectation of at least six months following Phase 1. We don't think an internal non-specialist can do this. The technology keeps changing and staying current is somebody's job. If your strength is implementation and your interest ends at handoff, we're probably not a good match. The build is the way in. The ongoing cycle of listening and improving is the work. OUR ENVIRONMENT Windows. Gmail is our system of record. Slack with 10 to 20 active channels. Four-seat license pack, likely growing to five or six users. Documents in Dropbox with some local storage (outside Phase 1). No project tracking in place. WORKING ARRANGEMENTS Remote work on our systems with real content, under a named account we provision and can revoke. NDA signed before any data access — our agreement, not the platform default. All material returned or deleted at close unless a continuing agreement is in place. Someone local to Chicago is a mild preference, not a requirement. HOW TO PROPOSE Give us an hourly rate and an estimate of hours broken out across the deliverables above. We'll work not-to-exceed against that estimate. Include your proposed structure and rate for ongoing monthly support. Please do not send a single lump sum. We want to see where the hours go.

I need software engineer who can collaborate for AI training works.

### Job Description: AI Chatbot Developer We are excited to announce an opening for an experienced and innovative developer to join our dynamic team in the pursuit of creating an advanced AI Chatbot. This chatbot will be designed to perform essential business functions, including but not limited to lead generation, quoting, and providing exceptional customer support. Our ideal candidate will possess a robust background in AI technologies, particularly in the realm of chatbot development, and will be equipped with outstanding problem-solving skills that enable them to tackle complex challenges with creativity and efficiency. As a key member of our development team, you will collaborate closely with various departments to gain a comprehensive understanding of our specific operational needs and requirements. Your ability to translate these needs into a functional and user-friendly chatbot solution will be critical to enhancing our overall operational efficiency. We are looking for someone who is not just technically proficient but also possesses a keen sense of business acumen to ensure that the chatbot aligns with our strategic goals. In this role, you will be responsible for various aspects of the chatbot development lifecycle, including but not limited to: - Designing and developing the conversation flow and user interface of the chatbot, ensuring it is intuitive and engaging for users. - Implementing natural language processing (NLP) capabilities to enable the chatbot to understand and respond to user inquiries accurately. - Integrating the chatbot with existing systems and databases to facilitate seamless access to information necessary for lead generation, quoting, and customer support functions. - Conducting rigorous testing and quality assurance to ensure the chatbot performs reliably and meets user expectations. - Analyzing user interactions and feedback to continuously improve the chatbot's performance and expand its capabilities over time. - Staying current with the latest advancements in AI technologies and chatbot development to incorporate best practices and innovative solutions. You will also play a crucial role in training team members on how to utilize the chatbot effectively and will be expected to provide ongoing support and maintenance to ensure the chatbot remains up-to-date and functional. If you have a passion for artificial intelligence, a deep understanding of customer engagement strategies, and a desire to make a significant impact within our organization, we would love to hear from you! Join us in revolutionizing the way we interact with our customers and streamline our business processes through cutting-edge technology. This is a fantastic opportunity for someone looking to advance their career in a fast-paced, forward-thinking environment. Apply today and be part of our exciting journey towards enhancing our customer experience through AI!