Job workflow

Updated on Aug 25, 2016 in [I] MicrojobEngine
13 on Mar 15, 2016

There seems to be a bit of a confusion on a job order page.

Current Process Buyer:

  • Buyer chooses a provider
  • Buyer orders service
  • Buyer pays for the service to the website owner
  • Buyer gets re-directed to the job page after payment (the brief details are not using any <br> / <p> here and all text of the service description is scattered and not very nice to read)
  • Buyer has to know that he needs to click on a small button on the right side saying “contact me” to provide details to the provider. (The big button which comes to the attention is the DISPUTE button – which from UX perspective it should have normal importance for visibility to less importance as visibility)

Current Process Provider:

  • Provider get’s the e-mail that a new order came in
  • Provider needs to wait for the buyer to provide feedback of what he wants (always if the buyer understands that he needs to provide the brief by clicking on a hidden button.
  • Once the provider get the information and has work done he needs to go to the messages which are in no way connected to the job order and upload the images as a message.
  • Once the client is happy with the logo the provider needs to go to the job page and upload the final files in the job page this time.

NEW Process Buyer:

  • Buyer chooses a provider
  • Buyer orders service
  • Buyer pays for the service to the website owner
  • Buyer gets re-directed to the job page where he needs to provide the brief description as required by the provider
  • The Job Page should have a messaging system in which the buyer and provider can communicate and keep everything in place in one simple page (just like fiverr or http://envatostudio.go2cloud.org/SH1K )
  • Buyer should have the option to reply to the provider in the same page with a message or have another button which will approve the job

NEW Process Provider:

  • Provider get’s the e-mail that a new order came in
  • Provider logs into the order page and sees the brief or asks the buyer to provide the brief through the messaging system in the job page.
  • Once the samples are ready the provider can send the samples over to the buyer via the messaging system
  • Once the job gets approved the provider will send the final files to the buyer via the messaging system

Please vote so we get a proper and organized system otherwise we will be spending 70% of the time with customer support instead of promoting and evolving the site 🙂

Thanks

  • Liked by
  • Branko Curcic
  • Jaro Kunderak
  • Jeffry Cheng
  • Maurice Pennington
  • Daniel Nguyen
  • +1
0 on Mar 15, 2016

Hi CZD (or Chirs if I have to guess), 

We understand that the current flow of 1.0 does not fit all customers. We also understand that we have to collect another important point of view (your as an example) to improve the product as you may wish. 

Actually we had a chance to think about your idea at the first step. Let’s wait until we know what people think. Thank you. 

Keep posted. 

 

  • Liked by
Cancel
1 on Mar 15, 2016

I totally agree with

That would be a much better user friendly work-flow.

 

Admin Admin
on Mar 16, 2016

Sure Miguel. 

Show more replies
  • Liked by
Cancel
0 on Mar 18, 2016

I agree with CZD. Please incorporate CZD’s suggestion in the next update. RIght now, the theme I have is really really basic. It has the basic functionality but what’s important now in a successful company is more than that. I thought I was getting a lot features. =(

  • Liked by
Cancel
1 on Mar 19, 2016

Hi all, 

I have a good news: We already have a technical solution for this. But to make sure we’re in the right track, I would like to ask you something: If you can draft or send us some flows/diagrams, this will help us learn how to balance the ideas vs. the scope of the theme itself. 

Best, 

 

Customer Customer
on Mar 19, 2016

Hi Shinya. I’ll gladly do that. I have some more valid points which need to be addressed.

Pausing of a Service: If a provider wants to go on holiday he needs to be able to pause the service and shift it to draft / unpublished. Important that the jobs already started associated with the service keep on going as normal though.

Approval / Decline of a Job: It’s important for the buyer to know if the provider is willing to work on his request. Prior to start the job the provider should click on a SUBMIT or DECLINE button to indicate the buyer that he started / accepted the job.

If a buyer does not get any feedback from the client within a reasonable time then the buyer would have the option and button to CANCEL the job. This is because if you order a $100 logo and need it a bit urgent you would love to know whether the provider is interested in working with you or not. 

If not the client can CANCEL the job and get the money credited into his wallet. From there he can use that money to purchase another service.

Automatic Job Closing: If the provider is getting a lot of orders, it’s a bit of a problem for him to manage quality of work and back office work at the same time. It’s important that the admin sets a date on when a job should close automatically if there is no feedback from either the buyer / seller.  Once feedback is given the timer would reset back to the amount of dates set by the admin.

Notification E-mails: E-mails need to be sent whenever a buyer / provider provide feedback or message each other (both during a job or if they send a message to each other via the site). Emails should be sent out whenever an action is performed on the site.

Disputes: Admin needs to have the ability to choose to re-open the job rather then just close it in favour of the buyer / seller. There might be room for arrangements in most cases and it’s just a matter for a judging entity to point that out to both the buyer and the seller. At the end you don’t want a site were people will not get paid for work they did or pay for work they are not happy with. We try and make them happy both.

Invoices: No invoices are being sent out from the system on completion of a job. This is very important feature to have because it’s the law.

  • Invoice Buyer: should get invoice from the buyer with both Billing Details set in their profile
  • Invoice Seller: Once the job has been approved the client should be sent an invoice coming out from the Site Admin. The amount of the invoice should be AMOUNT OF SERVICE – % COMMISSION taken by admin.

Thank you for your time and dedication.

Show more replies
  • Liked by
Cancel
3 on Mar 19, 2016

Hi I tried my best to explain the above in a very logical way. Please feel free to contact me if you need any clarification.

I’m a freelancer working on freelance sites for the past 3 – 5 years full time and I know the process both buyers and freelancers are used to and expect to have in a site like this 🙂 

Hope it helps

Customer Customer
on Mar 19, 2016

The TIME PASSED is referring to this point: 

Automatic Job Closing: If the provider is getting a lot of orders, it’s a bit of a problem for him to manage quality of work and back office work at the same time. It’s important that the admin sets a date on when a job should close automatically if there is no feedback from either the buyer / seller.  Once feedback is given the timer would reset back to the amount of dates set by the admin.

Admin Admin
on Mar 26, 2016

Hi Chris, I and the team have had a chance to look at your diagram and see that there must be something more for the current 1.0 flow. I cannot give 100% guarantee based on your workflow, but we planned to do something (at this moment in order to sync. the future versions):

  • 1.0.3: update withdraw flow to make it more logical and some tiny improvements.
  • 1.0.4: update communication within an order. There’s also a countdown to notify the progress. Some tiny improvements as well.

I personally like the automatic job closing & the re-open function of the admin, but the fact is the team has to do research to overcome some specific constraints of the framework (WordPress). Let see how far we can go. Keep posted.

Customer Customer

Thanks Shinya, I’m glad to see there is an update coming.

Chris’s diagram and workflow is what I was hoping to see as well, very much closer to how Fiverr works. 

The most critical elements I see are the ones right at the beginning that give the user ‘next steps’ and start conversation with the seller, having the seller accept to start working on the project.

One thing I would add is on the job page to have the system ask the user for any requirements that are set by the seller. So if the seller is doing.. for example… a voiceover. They need a script for what to read. So the seller could set a requirement as “Need your script for what to read”. 

Once the buyer completes payment and is taken to the job page, the system auto posts in the chat what the seller requires to start the project. And then the buyer must upload/post those required assets before the project begins. 

 

Show more replies
  • Liked by
Cancel
0 on Mar 19, 2016

Is it possible to have “I will….” a default gig description starting words???
This is to keep the uniformity on the site.

 

  • Liked by
Cancel

Thanks for posting your workflow Chris and the diagram. I suggested a similar workflow a while back in this thread here: http://forum.enginethemes.com/thread/buyer-user-flow/

The ‘chat’ system once order has been made is the most critical piece IMHO. Similar to Fiverr. Because right now it’s confusing when they buy and it doesn’t really take them anywhere that explains next steps.

  • Liked by
Cancel
0 on Aug 25, 2016

Hi,

Just came across this post. 

Has this been implemented (or at least partially) already in version 1.1.1?

Thanks,

  • Liked by
Cancel
Loading more replies
Posting & Replying function will be deactivated from 3pm GMT+7 12th Sep.
Read More