Follow up on Consensus HK Campaign until 18Feb

[minhyeong112]

Time Estimate

• I have added a time estimate label

Background Information

The Consensus HK campaign, kicked off in #114 needs daily follow ups for the next 10 days

Goal: book at least 2 warm lead appointments per day at Consensus HK (use link below)

Relevant Links

Meet Ubiquity at Consensus Hong Kong

[0x4007]

I'm less optimistic about manning follow ups during the conference but let's see. We arrive in eight days (15 February)

[minhyeong112]

for sure! maybe just "fund" the proposals that you want?
(again, just thinking out loud here to try to come up with a standard format for "recurring" tasks over extended periods of time. presumably, base pay covers these sorts of things but I know you mentioned wanting to move towards 100% incentives)

[0x4007]

We'll consider this a research exercise and hopefully come up with something interesting.

In theory if the services you use have apis then we can monitor webhook events and credit as we do for routine tasks like pull reviews here on GitHub. If you find relevant docs please link them.

Then you don't need to make these repetitive tasks but instead you'll receive direct rewards based on the actions you took.

I suppose that implementing these webhook listeners would make more sense for org functions that require a lot of man power. For example we have like ten developers so it makes sense to automate these things.

The next department I would imagine that we might need to scale is more sales related vs lead generation. In which case it most likely would have to deal with parsing meeting transcripts.

[minhyeong112]

monitor webhook events and credit as we do for routine tasks

totally agree!! that would be awesome and I imagine very useful for sales people everywhere
maybe there's a strong use case for a UbiquityOS HubSpot integration once we get that thing working smoothly.

[0x4007]

monitor webhook events and credit as we do for routine tasks

totally agree!! that would be awesome and I imagine very useful for sales people everywhere
maybe there's a strong use case for a UbiquityOS HubSpot integration once we get that thing working smoothly.

Happy to do research once we have an SOP that yields results.

[minhyeong112]

based on this feedback, just closed all the sub-tasks since it was more cumbersome to manage, will provide updates on this thread instead.

will add <1day label here instead, in order to cover:
-following up every day (~15 min/day)
-2-3 adjustments to the campaign to cover: adjusting copy, finding new leads, linking up with nReach staff, fixing integrations that don't work properly, basically anything to keep the outreach machine running**note: we will need less "adjustments" in the future as we develop the SOPs (2 hours/adjustment)

[ubiquity-os]

! Pricing is disabled on parent issues.

[minhyeong112]

oops 😅

[0x4007]

! Pricing is disabled on parent issues.

@gentlementlegen looks like we got a straggler diff perhaps we can make a single task to upgrade all the bot formatting across all plugins in one shot.

[0x4007]

I estimated each at ten minutes not sure if thats accurate @minhyeong112

[gentlementlegen]

! Pricing is disabled on parent issues.

@gentlementlegen looks like we got a straggler diff perhaps we can make a single task to upgrade all the bot formatting across all plugins in one shot.

Yes I can take care of that, I know that plugins like command-ask however would require a lot of changes.

[minhyeong112]

I estimated each at ten minutes not sure if that's accurate

fair enough! (I was counting in all the "process/SOP development" but that will go away for future campaigns anyway)
the basic framework for "a campaign" will be:

Launch (1 proposal, usually hours, max 1 day for a complex one)
Follow up (1 proposal, minutes per day, totaled up for one timestamp that roughly covers) - will require daily updates with unlimited "top-ups" for now so as not to be unassigned due to time (e.g. 2 hour task executed in 10-5 minute chunks over the next X days)

[minhyeong112]

/stop

[ubiquity-os]

Caution

You are already assigned to this task.

[minhyeong112]

/start

[ubiquity-os]

Beneficiary

0xe580eF1f6f333145180e9c498036EEE38bA6F7f5

Tip

• Use /wallet 0x0000...0000 if you want to update your registered payment wallet address.
• Be sure to open a draft pull request as soon as possible to communicate updates on your progress.
• Be sure to provide timely updates to us when requested, or you will be automatically unassigned from the task.

[ubiquity-os]

Important

• Reminders will be sent every 2 days and 8 hours if there is no activity.
• Assignees will be disqualified after 4 days and 16 hours of inactivity.

[0x4007]

I estimated each at ten minutes not sure if that's accurate

fair enough! (I was counting in all the "process/SOP development" but that will go away for future campaigns anyway)
the basic framework for "a campaign" will be:

Launch (1 proposal, usually hours, max 1 day for a complex one)
Follow up (1 proposal, minutes per day, totaled up for one timestamp that roughly covers) - will require daily updates with unlimited "top-ups" for now so as not to be unassigned due to time (e.g. 2 hour task executed in 10-5 minute chunks over the next X days)

@gentlementlegen as a heads up we might need to disable max top ups based on collaborator/contributor status. Mig would need unlimited top ups to track a long campaign.

If you need to break it out to a new task you can use this comment.

[minhyeong112]

We just got our first Calendly booking 🎆

[gentlementlegen]

@0x4007 I made an option already to disable this behavior, but it totally disables this on the whole repo, would that be enough? If not, I'll make a new task then.

[0x4007]

I think based on the original vision of why we implemented the feature in the first place, it would make sense to allow for us to target contributors specifically and avoid collaborators.

However if we implement command-deadline then we can use it as a cap for collaborators selectively per task.

[gentlementlegen]

We could, but I think it should apply to all because it would enforce deadlines. I can eventually add a configurable element for this, but that would apply per repo not per task.

Doing this selectively per collaborator would require storage.

[ubiquity-os]

@minhyeong112, this task has been idle for a while. Please provide an update.

[minhyeong112]

so massive update on nReach...
their TG webapp thing below is not reliable

the good news is that I had some interested people to reply to when I connected the TG they gave us to the TG desktop app
just added @0x4007 to a few groups, and would have added you to more but I don't have permissions to add people if the lead is the one that started the group
anyway, will hopefully get an uptick in appointments and groups made soon

[0x4007]

Be sure to tell their support!